claude-session-continuity-mcp

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden and does so well. It discloses key behavioral traits: side effects (writes to sessions table, updates active_context record), idempotency (multiple calls overwrite previous record), and automatic restoration mechanism. No contradictions exist.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with core purpose in first sentence. Every subsequent sentence adds critical behavioral context (persistence details, side effects, idempotency). No redundant or verbose language. Efficiently structured for agent comprehension.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations and no output schema, the description provides strong behavioral transparency and usage context. It covers persistence mechanism, side effects, idempotency, and restoration flow. Minor gap: doesn't specify error conditions or what happens if project doesn't exist.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, providing detailed parameter documentation. The description adds minimal value beyond schema by listing what gets persisted (summary, completed work, etc.), but doesn't explain parameter interactions or constraints. Baseline 3 is appropriate given high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with specific verbs ('save', 'end', 'persists') and resources ('session state', 'SQLite', 'sessions table'). It distinguishes from sibling tools like session_start (which restores) and session_history/search_sessions (which query past sessions).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use ('before ending a conversation') and when not to use (implies not for querying or restoring). Names the complementary tool session_start for restoration, providing clear alternatives. No misleading guidance is present.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.