artwork_job_cancel

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

The description discloses a meaningful behavioral trait: cancellation is cooperative and deferred to the next safe step boundary rather than abrupt. With no annotations, however, it does not cover permissions, reversibility, side effects on output, or whether cancellation is idempotent – important context for a state-changing job tool.

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?

One sentence, front-loaded with the verb and resource, with no filler. It is appropriately sized for the action and every word earns its place.

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?

An output schema exists, so return values need not be explained. But with no annotations, a mutation tool, and an undocumented parameter, the definition should do more to explain prerequisites, effects on a running job, and result handling.

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 single job_id parameter has 0% schema description coverage and the description does not explain its expected format or source. The parameter name is self-evident, but the description adds no semantic detail beyond the schema and does not compensate for the coverage gap.

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, 'cancel', and resource, 'artwork job', and the 'next safe step boundary' scope hints at a distinction from an immediate kill. It does not name sibling tools such as artwork_job_pause or artwork_job_resume as alternatives, so differentiation is only partial.

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?

No explicit when-to-use or when-not-to-use guidance is provided. The safe-boundary phrasing implies cancellation is not immediate, but it does not tell the agent when cancel is preferable to pause/resume or how to handle an already finished job.

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