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

No annotations are provided, so the description carries the full burden and does so well: it discloses what is destroyed (pending/staged changes), what survives (already-applied changes), the dual-mode response (stop_state stopped_here vs accepted), the required polling loop with a concrete termination condition (metadata.stopped_unwound or terminal status), and the 409 error behavior.

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?

Purpose is front-loaded in the first sentence, then behavior, then usage, then response semantics. Dense but nearly every clause adds operational value. Slightly long middle sentence about stop_state could be tightened, but nothing is filler.

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?

With no annotations and no output schema, the description still conveys the mutation semantics, the response shape, and the async polling protocol, which is the critical missing structured data. The main residual gap is the undocumented authorization parameter and how to obtain a valid job_id.

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% for both parameters. The description never explains job_id (format, where to obtain it — presumably list_jobs/get_session_jobs) nor the optional authorization parameter, which is entirely unaddressed. With zero schema coverage, this is a real gap the description should have filled.

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?

States a specific verb+resource — stops a running turn or ends a turn awaiting review by discarding staged changes — and clarifies the scope boundary (applied changes preserved, pending changes discarded). This is immediately distinguishable from siblings like get_job, list_jobs, or approve_change.

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?

Explicitly names the triggering conditions (user changed their mind, retry with different parameters or model_tier) and the negative case (a turn that already finished cannot be stopped and returns 409). It also routes the agent to the correct follow-up action by naming get_job as the polling tool for the accepted case.

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