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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description is not the sole safety carrier. It nonetheless adds meaningful context beyond the annotations: the exact irreversibility semantics ('a cancelled job cannot be moved back to any other status') and a required confirmation ritual before invocation.

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, zero padding, and the irreversible/destructive warning is front-loaded immediately after the purpose statement. Every clause carries actionable 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 mutation tool with no output schema, the description supplies the critical missing pieces: irreversibility, the pre-call confirmation requirement, and the reason to forward. An agent has everything it needs to call this safely.

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 67%, between the low and high baselines. The description reinforces the reason parameter ('pass the reason they gave') and implies job identification, but says nothing about the optional brand parameter, whose refusal behavior is documented only 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 and resource ('Cancel a job'), which is unambiguous against siblings like create_job, get_job, and schedule_job. It does not explicitly name a sibling to distinguish from, but the verb alone is sufficiently distinct for selection.

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 a clear precondition workflow: name the job and customer back to the user, get an explicit yes BEFORE calling, and pass the reason they gave. That is strong when-to-use guidance, though it names no alternative tool for cases where the agent should not cancel.

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