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

With annotations already covering readOnly=false, destructive=true and openWorld=true, the description still adds auth requirements, failure semantics (cleanup failure leaves it active, busy subject refused), side effects (finalizes unfinished runtime iterations, holds legacy tasks, records owner/reason) and authority boundaries. The claim that 'a repeat returns the same receipt' sits in mild tension with idempotentHint=false, though it describes response behavior rather than effect-level idempotency.

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 purpose is front-loaded in sentence one and every subsequent sentence carries substantive information (preconditions, failure modes, authority limits) rather than filler. The second paragraph is a dense run-on sentence with heavy jargon ('binds the runtime', 'busy subject'), which costs some parsability.

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?

Return values need not be explained since an output schema exists, and annotations cover the safety profile. For a destructive mutation the description supplies preconditions, failure behavior, side effects and authority boundaries, leaving only the precise mechanics of what 'cleanup' performs and project_id's role underspecified.

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 0% - parameters carry only bare titles. The description partially compensates by explaining that the exact project iteration number binds the runtime and that the reason is recorded against the owner. project_id receives no explanation at all, so the compensation is incomplete for three undocumented required parameters.

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 opening sentence gives a specific verb (stop), resource (one running iteration) and scope qualifier (after confirmed runtime cleanup). It is clearly distinct from siblings like close_task, replan_task or cancel_roadmap_item. However, it never names an alternative tool, so sibling differentiation must be inferred from domain knowledge rather than the text.

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?

Preconditions and exclusions are stated explicitly: a personal active workspace owner is required, and workspace keys/Portfolio delegation cannot stop compute, plus a busy subject is refused. This is real when-to-use guidance, but no alternative tool is named for the cases it excludes, so it stops short of full routing guidance.

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