Context Travel MCP

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It discloses behavioral traits by listing what the tool returns (turns, token count, compaction events, context age) and its purpose for decision-making. However, it doesn't cover aspects like performance, error conditions, or rate limits, leaving some gaps in 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 appropriately sized and front-loaded: it starts with the core purpose, lists returns in a bulleted format for clarity, and ends with usage guidance. Every sentence earns its place 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?

Given the tool's complexity (simple read operation with no parameters) and lack of annotations/output schema, the description is mostly complete. It explains what the tool does, what it returns, and when to use it. A minor gap is the absence of output format details, but this is mitigated by the straightforward return list.

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 tool has 0 parameters with 100% schema description coverage. The description doesn't need to add parameter semantics, so a baseline of 4 is appropriate as it compensates by providing clear output information and usage guidance without unnecessary parameter details.

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 verb ('Get') and resource ('statistics about your current context window health'), and distinguishes it from sibling tools by focusing on monitoring rather than manipulation (checkpointing, deleting, listing, resetting).

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: 'Use this to decide when you might want to checkpoint or reset.' It provides clear context for usage and distinguishes it from sibling tools by indicating it's for decision-making before taking actions like checkpointing or resetting.

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