Context Continuation MCP Server

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 states the tool generates a prompt but doesn't explain what the prompt contains, how it's formatted, whether it's read-only or has side effects, or any permissions or limitations. This is inadequate for a tool with potential behavioral implications.

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 a single, efficient sentence that directly states the tool's function without unnecessary words. It's front-loaded with the core action and resource, 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 complexity (generating a prompt for context restoration), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what the prompt looks like, how it aids 'continuing work', or what behavioral traits to expect, leaving significant gaps for an agent to understand its use.

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?

The input schema has 1 parameter with 100% description coverage ('Path to project directory'), so the schema fully documents the parameter. The description adds no additional parameter information, but with 0 parameters needing compensation and high schema coverage, the baseline is 4 as it doesn't detract from the schema's clarity.

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 states the tool 'Generate[s] a context restoration prompt for continuing work', which provides a clear verb ('Generate') and resource ('context restoration prompt'). However, it doesn't specify what format the prompt takes, what 'context restoration' entails, or how it differs from sibling tools like context_get_status or context_start_session, leaving the purpose somewhat vague.

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 offers no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., after a session ends), exclusions (e.g., not for initial setup), or comparisons to siblings like context_get_status for checking current state, leaving the agent with no usage context.

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