claude-session-continuity-mcp

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key traits: the semantic search mechanism (multilingual embeddings, 94+ languages), fallback to FTS5 keyword search, and read-only nature. However, it lacks details on rate limits, error handling, or performance characteristics that could further aid the agent.

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?

The description is front-loaded with the core functionality, uses efficient sentences with zero waste, and includes only essential details like the multilingual support and fallback behavior. Every sentence earns its place by clarifying usage or capabilities.

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?

Given the tool's complexity (semantic search with fallback) and lack of annotations or output schema, the description does a good job covering key aspects like purpose, usage guidelines, and behavioral traits. However, it could be more complete by mentioning output format or potential limitations, which would help the agent better anticipate results.

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%, so the schema already documents all parameters (query, project, limit). The description adds minimal value beyond this, as it doesn't provide additional context on parameter usage or constraints. The baseline of 3 is appropriate since the schema handles the heavy lifting.

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 ('semantic search across session history') and resources ('session history'), and distinguishes it from sibling tools by contrasting with 'session_history' for recent sessions only. It explains the unique semantic approach using multilingual embeddings versus keyword matching.

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?

The description provides explicit guidance on when to use this tool (for semantic search by meaning) versus alternatives ('Use session_history instead when you just need the N most recent sessions'). It also clarifies the fallback behavior to keyword search when embeddings are unavailable, offering clear context for decision-making.

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