render_delete_all_jobs

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

The annotations already flag destructiveHint=true, so the description's added value is the return semantics: 'True if all jobs were deleted successfully.' However, it does not disclose partial-failure behavior (e.g., what happens if some jobs fail to delete) or whether rendering must be stopped beforehand.

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 short sentences, front-loaded with the action ('Delete all render jobs from the queue') followed by the return condition. Every sentence earns its place with no wasted words.

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?

For a zero-parameter destructive tool with a destructiveHint annotation and output schema, the description covers the core behavior and return value concisely. It leaves minor gaps around partial failure or stopping renders, but these are not critical for such a simple operation.

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?

There are zero parameters in the schema, so the description needs to explain none. The baseline of 4 applies because the tool correctly requires no input; the description adds no extra parameter information, but none is needed.

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 states 'Delete all render jobs from the queue' with a specific verb, resource, and scope. The word 'all' clearly distinguishes this from the sibling render_delete_job, which deletes individual jobs.

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 usage is implied by the phrase 'all render jobs' — an agent can infer this clears the entire queue — but there is no explicit guidance on when to use this vs. render_delete_job, nor any mention of prerequisites like stopping active renders first.

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