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 well by disclosing key behavioral traits: executes shell command in project directory, has 5-minute timeout, returns specific output format with last 1000 characters of stdout/stderr. However, it doesn't mention error handling or what happens if project doesn't 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?

Three sentences with zero waste: first states purpose with platform specifics, second describes side effects and return format, third provides usage guidance with alternative. Each sentence adds essential information without redundancy.

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 single-parameter tool with no annotations and no output schema, the description does well by explaining execution behavior, timeout, and return format. However, it doesn't clarify what happens when build fails or if there are specific prerequisites beyond project existence.

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. The description doesn't add any additional meaning about the 'project' parameter beyond what's in the schema, maintaining the baseline score for 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 specific action ('Run the project's build command') and resource ('project'), with explicit platform-specific commands provided. It distinguishes from sibling 'verify_all' by noting that tool runs build only, while verify_all combines build, test, and lint.

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 this tool ('Run the project's build command') versus when to use the alternative ('Use verify_all to run build + test + lint together'), providing clear guidance on tool selection based on desired scope of verification.

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