context

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

With no annotations provided, the description carries the full burden for behavioral transparency. While it lists operations and their parameters, it does not disclose side effects, persistence behavior, or resource constraints, leaving significant gaps for an agent.

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 with a lead sentence followed by a bulleted list of operations. It is relatively concise given the number of operations, though some repetition (e.g., 'For verify') could be streamlined.

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?

The description provides a good overview of operations and their parameters, but it lacks details on output/return values, error handling, and prerequisites. For a complex tool with 18 parameters and no output schema, this is adequate but not complete.

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 description adds meaningful context for many parameters by linking them to specific operations (e.g., 'For handoff_create: summary for next session'). This goes beyond the schema's brief descriptions, especially for the structured parameters like arrays, though some parameters like 'reason' lack context.

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 as 'Context protection for long tasks' and enumerates eight specific operations with brief descriptions, making it easy to understand what the tool does and how it differs from sibling tools like 'memory' or 'output'.

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 implies usage through operation names and parameter details (e.g., when to use checkpoint_save vs checkpoint_restore), but it does not explicitly state when to use this tool over alternatives or provide exclusion criteria.

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