art.production.cancel

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Cancel' without explaining whether cancellation is destructive, irreversible, audited, or whether it affects running operations. This is notably thin for a state-changing 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?

The description is a single concise sentence with no filler or repetition. It communicates the basic operation immediately, and given the single-parameter schema, the brevity is appropriate.

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 cancellation operation with no annotations and no output schema, the description is too sparse. It does not state the effects of cancellation, whether it can be reversed, what happens to existing production attempts, or how an agent should confirm success.

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?

The schema already documents the single parameter 'job_id' as a 'Production job ID' with 100% coverage, so the description does not need to add parameter detail. It adds no extra semantic meaning beyond what the schema provides, which keeps this at baseline.

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 clearly states the action and resource: 'Cancel a production job.' It is specific enough to convey the core purpose, though it does not explicitly differentiate itself from sibling art.provider.cancel or explain what qualifies as a production job.

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 about when to use this tool versus alternatives, nor any mention of prerequisites or exclusions. The description simply states the action without indicating whether the job must be active, pending, or in a particular state to be cancellable.

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