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: it discloses side effects ('executes a shell command with a 5-minute timeout'), return format ('Returns {success, output}'), and platform-specific behavior. It doesn't mention authentication needs or rate limits, but covers key behavioral aspects.

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?

Perfectly front-loaded with the core purpose, followed by platform details, parameter guidance, side effects, return format, and sibling differentiation. Every sentence earns its place with zero wasted words.

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 tool with no annotations and no output schema, the description provides excellent context: side effects, timeout, return format, platform detection logic, and sibling differentiation. The only minor gap is not explicitly stating this is a read-only operation (though 'executes a shell command' implies mutation).

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 baseline is 3. The description adds some context about the 'testPath' parameter ('Specific test file or directory to run'), but doesn't provide additional meaning beyond what's already in the schema descriptions for both parameters.

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: 'Run the project's test suite' with specific platform detection logic. It distinguishes from sibling tool 'verify_all' by explaining this tool runs tests only, while verify_all runs build + test + lint together.

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: 'Use verify_all to run build + test + lint together' establishes when to use this tool vs. the alternative. The description also indicates when to use optional parameters: 'Optionally scope to a specific test file or directory' and 'runs all tests if omitted'.

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