feat(mcp): add title and tags annotations to all MCP tool decorators (phase 1, #826)

[groksrc]

Closes #826

Summary

Implements Phase 1 of issue #826: adds title and tags annotations to all 23 @mcp.tool decorators across 19 tool files.

What changed:

• Every registered MCP tool now has a human-readable title= and at least one tags= set
• FastMCP 3.3.1 (already pinned in pyproject.toml) fully supports title, tags, and timeout in @mcp.tool — verified by inspecting the installed package's method signature before editing
• Tags used to categorize tools: notes (write/read/edit/delete/move/view), search (search_notes, search, fetch), projects (list/create/delete project), cloud (cloud_info, release_notes, list_workspaces), schema (validate/infer/diff), navigation (build_context, recent_activity, list_directory), canvas, ui
• timeout deferred: the issue brief narrowed Phase 1 to titles + tags only, and no specific timeout values were specified; FastMCP docs note that timeout behavior varies by transport
• output_schema explicitly deferred as Phase 2: requires per-tool design decisions about structured JSON vs. str|dict depending on output_format

How it was tested:

• Extended tests/mcp/test_tool_contracts.py with an async smoke test test_mcp_tools_have_title_and_tags that calls mcp.list_tools() and asserts every registered tool has a non-empty title and at least one tag, guarding against future regressions

Review notes

A few minor items worth a quick look:

1. Tag taxonomy and title placement deviate from the issue's literal proposal. The issue showed title nested inside annotations={...} and tags like content/graph. This implementation uses top-level title=/tags= kwargs (the FastMCP 3.x-native, arguably better approach) and renamed categories to notes/navigation. Reasonable and documented above, but a reviewer diffing against the issue will notice.

2. Count framing in the summary is slightly off. The summary says "23 decorators across 19 files", but the diff also annotates 2 commented-out tools in ui_sdk.py (search_notes_ui, read_note_ui) which are NOT registered (their import is commented out in tools/__init__.py). The annotations are harmless dead-code consistent with the existing TODO pattern, but the count is slightly off.

3. Regression test has a subtle import dependency. Tools only register because test_tool_contracts.py has a module-level from basic_memory.mcp import tools import. Without that import, mcp.list_tools() returns 0 and the test would pass vacuously. The import is present, so the test is valid today, but a short assert tool_list (non-empty) guard or a comment would harden it against accidental import removal.

🤖 Generated with Claude Code