delete_render_job

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds meaningful context: it explains what idempotency means here (already_absent:true instead of failure), calls out headless-safety, and lists the exact return shape. It does not cover auth or side effects beyond the queue, keeping it short of a 5.

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 front-loaded with the core action and then efficiently layers in modes, idempotency, and return values. Every sentence contributes, though the inline return-shape block is slightly dense and could be separated.

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 tool's two-mode delete behavior and the absence of an output schema, the description is complete: it covers both operating modes, headless-safety, idempotency semantics, and the exact response fields an agent will see. Nothing additional is needed to invoke it correctly.

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 100%, so both parameters are already documented. The description adds implementation detail (UMoviePipelineQueue::DeleteJob vs DeleteAllJobs and 'delete_all clears the whole queue and ignores job_name'), but this mostly restates schema semantics, making the baseline 3 appropriate.

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 (Deletes) and resource (a job from the editor Movie Render Queue) with two explicit modes: delete one job by name or clear the whole queue. The purpose is unambiguous, but it does not explicitly differentiate itself from siblings such as cancel_render_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?

The description implies when to use this tool (removing jobs from the render queue) and notes it is headless-safe, but it never states when-not to use it or names alternatives like cancel_render_job. Usage guidance is implied rather than explicit.

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