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

Annotations confirm a destructive, non-idempotent, open-world write, and the description goes well beyond them: it explains exactly what is cancelled, that workers who already accepted still receive the cancellation fee, that already-handed-over steps remain payable, and that an unstarted chain refunds everything held. That is precisely the consequence detail an agent needs before invoking a destructive operation.

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?

Four sentences, no filler, and the primary action is front-loaded before the mode-specific consequences. The prose is dense and relies on back-references, but every sentence carries distinct 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 destructive, non-idempotent chain operation with no output schema, the description covers outcomes and the unstarted-chain edge case well, which is what an agent most needs. It does not say what happens on an invalid/finished chain id or what the call returns, a minor gap given no output schema is declared.

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 coverage is 100%, so the baseline is 3, and the description earns above it by explaining what the `mode` values actually do and what `deliverable` replaces ('instead of handing it on') rather than restating field names. It adds no details for `reason`, but that parameter is self-explanatory in the schema.

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 states a specific verb+resource ('End a chain') and immediately distinguishes its two modes, 'abort' and 'end_early', with concrete semantics for each. It does not explicitly name the neighboring tools (cancel_task, create_task_chain, reschedule_chain_handoff), so an agent must infer the boundary itself, but the chain-level scope is unambiguous.

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 guidance on which mode to pick and states a real precondition ('A chain that has not started can only be aborted'). What is missing is explicit routing against alternatives such as cancel_task for a single task, so the when-to-use-this-tool-vs-sibling decision is left to inference.

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