cancel_job

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

The description implies a state-changing operation but does not disclose side effects, idempotency, error conditions, or what happens upon cancellation. With no annotations, the description fails to provide sufficient behavioral context.

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 sentence, which is concise, but it is too terse and omits essential information. Conciseness should not compromise clarity; here it does.

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?

Given the complexity of the domain (scene jobs) and the presence of many sibling tools, the description is insufficient for an agent to use the tool correctly. It does not mention required job states, potential failures, or integration with other tools.

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%. The description adds no meaning for the sole parameter 'job_id', leaving the agent to infer its format or source. No explanation of how to obtain the job ID is provided.

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 verb 'Cancel' and the resource 'queued scene job', distinguishing it from sibling tools like run_scene or get_job. However, it does not specify that only jobs in 'queued' state can be cancelled, which limits precision.

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 guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites (e.g., job must be queued), when not to use it, or comparisons to sibling tools like get_job or run_scene.

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