cancel_media_job

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

Discloses that local worker is stopped, upstream quota may continue, and the job is not auto-retried. With no annotations, the description carries the burden and does so adequately.

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 concise sentences with no redundant information; purpose and caveat are clearly front-loaded.

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?

Covers the action, side effects, and status outcomes. Missing details like error handling for non-existent jobs or return values, but acceptable for a simple tool.

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 description does not clarify the job_id parameter (e.g., format, source) despite 0% schema coverage. The parameter is simple, but additional context like 'obtained from list_media_jobs' would improve usability.

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 specific verb 'Stop' and resource 'local worker for a queued/running job', distinguishing it from sibling tools like list_media_jobs and start_website_video.

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?

Provides context on upstream quota consumption and job status outcomes, but does not explicitly state when not to use the tool or alternative approaches.

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