delete_batch

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

Annotations already indicate `destructiveHint: true` and `idempotentHint: true`. The description adds the key behavioral detail that the tool only succeeds on ended jobs, preventing misuse on active jobs.

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 concise (two sentences) and front-loaded with the core action. It could be extended slightly to cover error cases, but it is efficient overall.

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 simple destructive tool with one parameter and annotations covering safety, the description is complete enough. It specifies the constraint and parameter origin, and the output schema exists, so return values are handled elsewhere.

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 schema has 0% coverage for parameter descriptions, so the description carries the burden. It explains that `name` is the batch job name from `create_batch`, which adds context but no further details about format or constraints.

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 tool deletes a batch job, with the specific constraint that it only works on ended jobs (succeeded/failed/cancelled). This distinguishes it from the sibling `cancel_batch` which targets active 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?

It explicitly says 'Only works on ended jobs,' guiding the agent not to use it on active jobs. While it doesn't name the alternative explicitly, the sibling `cancel_batch` is implied for active jobs.

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