Delete image template

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds genuinely new behavior: provider scopes, locks and credits apply, a mandatory confirmation gate before provider execution, and 'one submission only'. This meaningfully extends beyond the structured hints, though 'scopes, locks and credits apply' stays vague about which scopes or how credits are consumed.

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?

Three compact clauses with the endpoint front-loaded, and the most operationally important constraint (mandatory confirmation) placed before the trailing 'one submission only' note. No filler, though the middle clause is somewhat boilerplate.

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 destructive, non-idempotent mutation with no output schema, the description covers the confirmation gate and one-shot semantics, and annotations cover the safety profile. It stops short of stating irreversibility consequences or failure modes, but an agent has enough to call 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?

With 67% schema description coverage, the schema already explains 'account' and 'confirm' in detail. The description only indirectly gestures at the confirm flag via 'Mandatory confirmation before provider execution' and says nothing about the uid format or the account fallback rule, so it adds little parameter-level value.

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 leads with 'DELETE /v5/image_templates/{uid}', giving a specific verb (delete), resource (image template) and identifier. This is immediately distinguishable from siblings like delete_animation_template, delete_workflow and delete_webhook, which target other resources.

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 states the operation is the 'Current Bannerbear V5 operation' and that confirmation is mandatory before execution, implying usage context, but never names when to prefer this over fetch/update alternatives or what precondition (e.g. verifying the template exists or has no active publications) should be checked first.

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