audio_job_cancel

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

With no annotations, the description carries the full burden of behavioral disclosure. It says 'Cancel or suppress' but does not clarify whether the job actually stops, whether results are simply hidden, whether cancellation is reversible, or what happens if the job has already completed. The ambiguity between 'cancel' and 'suppress' is a significant omission.

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 a single tight sentence with no filler. It front-loads the action and resource efficiently, which is ideal for quick agent scanning.

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 potentially destructive async-job operation with no annotations and no output schema, this description is too incomplete. It does not explain confirm behavior, post-conditions, idempotency, or error scenarios. An agent would need to guess or inspect sibling patterns to call it 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 description coverage is 0%, so the description must compensate, but it adds no parameter-level meaning. It never mentions the required 'jobId' semantics in a useful way and completely omits the 'confirm' parameter, which likely controls confirmation of a destructive action. The schema's type/format hints are all the agent has.

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 uses a specific verb ('Cancel or suppress') and names the resource ('result of an asynchronous analysis job'), so an agent understands the core action. It does not explicitly distinguish it from sibling tools like audio_job_status or rew_measurement_cancel, but the async job scope is reasonably clear.

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?

There is no guidance on when to use this tool versus alternatives, such as audio_job_status for checking job state or rew_measurement_cancel for a different kind of cancellation. The description implies it applies to asynchronous analysis jobs, but no explicit when/when-not conditions are provided.

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