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 states the tool is 'Read-only' (safety profile), describes the return format ('structured JSON object'), and mentions what data is included. However, it lacks details on error handling, rate limits, or authentication needs, which would be beneficial for full transparency.

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 purpose, followed by usage guidelines, all in two efficient sentences with zero wasted words. Each sentence adds clear value, making it highly concise and well-structured.

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 moderate complexity (read-only status check with one parameter) and no output schema, the description is mostly complete: it covers purpose, usage, behavior, and return format. However, it could improve by mentioning error cases (e.g., if the project doesn't exist) or response structure details, slightly reducing completeness.

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 the single parameter 'project' with its type and description. The description does not add any additional meaning or context about the parameter beyond what the schema provides, such as examples or constraints like valid project names, which aligns with the baseline score when schema coverage is high.

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 specific action ('Get') and resource ('project's current status'), with detailed components like completion percentage, task breakdown, recent session activity, and active blockers. It distinguishes from sibling tools by contrasting with session_start for bootstrapping and positioning this for mid-session status checks.

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?

Explicit guidance is provided on when to use this tool ('mid-session status checks') and when to use an alternative ('use session_start instead when bootstrapping a new conversation'). This directly addresses sibling tool differentiation and context-specific application.

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