Pause session

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

Annotations already signal non-read-only and non-destructive. The description adds useful behavioral details: stopping the budget clock and preserving in-flight claims, plus optional handoff notes. This goes beyond the annotation baseline and enriches the agent's understanding of side effects, even though it doesn't cover auth or rate limits.

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?

Two sentences with no redundancy. The core action is front-loaded, and behavioral details follow immediately. Every word earns its place; there is no filler or extraneous 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?

Given the presence of an output schema, return values need not be explained. The description covers the essential behavior (pausing, budget clock, in-flight claims, handoff notes) and correctly restricts to active sessions. Missing details like error handling are minor for a state-change tool of this simplicity.

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 67%, so the baseline is 3. The tool description reiterates the purpose of the notes parameter ('Optional handoff notes'), which aligns with the schema's own description, adding little new meaning. The reason parameter remains undocumented in both places, so the description does not fully compensate for the coverage gap.

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 action ('Pause an active session') and adds specific behavioral consequences ('Stops the budget clock and keeps in-flight claims'), which distinguishes it from siblings like resume_session and stop_session. The mention of handoff notes further clarifies its purpose without ambiguity.

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 implicitly indicates usage by describing the pause behavior (stops budget clock, keeps claims) which suggests a temporary halt compared to a stop. However, it does not explicitly state when to use this tool instead of alternatives like stop_session or resume_session, nor does it mention exclusions. Sibling context helps infer, but it falls short of explicit guidance.

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