Resume session

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

With annotations already indicating this is not read-only and not idempotent, the description adds useful behavioral detail: it recovers in-flight units to pending with their checkpoints and returns the handoff. It doesn't cover auth or failure side effects, but it goes beyond annotation data.

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 four short, focused sentences that front-load the main purpose, then add optional behaviors, recovery semantics, and return value. No filler or redundant restatement of the tool name.

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 4 parameters, full schema coverage, and an output schema, the description covers the operation, optional modifications, recovery side effect, and return value. Nothing an agent needs to call it correctly is missing.

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 100%, so the parameters are already fully documented. The description mentions mode and budget but only echoes the schema; it doesn't add new semantic meaning to any parameter.

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 names a specific verb and resource ('Resume a paused, halted or interrupted session from its handoff'), which clearly distinguishes it from start_session, pause_session, and stop_session. It also states the optional mode/budget actions, so an agent can tell exactly what the tool is for.

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?

It gives clear usage context: use when a session is paused, halted, or interrupted, and optionally when you want to switch mode or add budget. It doesn't explicitly name start_session as the alternative for new sessions or list when-not conditions, so it stops short of a 5.

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