delete_render_jobs

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

With no annotations, the description provides minimal behavioral disclosure. It does not state whether deletion is permanent, if running jobs can be deleted, the impact on the queue, or authorization requirements. The phrase 'from the queue' adds some context but is insufficient.

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 short and to the point, with a clear header and args section. No redundant information. It efficiently communicates the core purpose and parameter behavior.

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 presence of an output schema (not shown), some return information may be covered elsewhere. However, the description lacks details on success/error states, confirmation, or side effects. For a deletion tool in a larger render workflow, more context would be beneficial.

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 explains the one parameter (job_ids) as optional with a default behavior of deleting all jobs if omitted. This adds value beyond the schema, which only defines the type and default null. However, it does not clarify behavior for empty arrays or other edge cases.

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 ('Delete') and the resource ('render jobs') with specificity ('from the queue'). It effectively distinguishes from sibling tools like add_render_job and get_render_progress.

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, such as canceling specific jobs versus all jobs, or considerations like whether jobs are already rendering. The only usage hint is that omitting job_ids deletes all jobs.

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