Context Travel 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 explains the tool's behavior: it resets context to a checkpoint, injects a handoff message that appears as if written just before reset, and describes what happens after calling ('your context will be restored to the checkpoint state plus your handoff message'). It doesn't cover potential side effects or error conditions, but provides substantial behavioral context.

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 well-structured and appropriately sized. It starts with the core purpose, then explains the handoff message feature with specific guidance on content, and concludes with the post-call effect. Every sentence adds value without redundancy, making it efficient and front-loaded with the most important information.

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 2 parameters, 100% schema coverage, no output schema, and no annotations, the description provides substantial context about the tool's purpose, behavior, and usage. It explains the unique handoff message feature thoroughly. The main gap is the lack of information about what happens to unsaved work or whether the reset is reversible, but overall it's quite complete for this complexity level.

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 100% description coverage, providing clear documentation for both parameters. The description adds some semantic context by explaining the purpose of 'message_to_self' ('briefing message for your future self') and what it should contain, but doesn't add significant meaning beyond what the schema already provides. This meets the baseline expectation 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 tool's purpose with specific verbs ('reset your context back to a saved checkpoint') and resources ('checkpoint'), and distinguishes it from siblings by mentioning the unique 'handoff message' feature. It goes beyond a simple reset operation by explaining the message injection aspect.

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 clear context about when to use this tool ('to reset your context back to a saved checkpoint') and what the handoff message should contain, but doesn't explicitly state when NOT to use it or mention alternatives like 'checkpoint_context' or 'delete_checkpoint' from the sibling list. The guidance is helpful but lacks explicit exclusion criteria.

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