Delete animation template

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

Annotations already declare destructive=true and idempotent=false, but the description adds operational context those fields do not carry: provider scopes/locks/credits apply, confirmation is required before provider execution, and the call is a single submission with no retry semantics. It stops short of describing what is actually destroyed (template vs. associated renders) or failure behavior.

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?

Front-loaded with the endpoint, then two short clauses covering cost/scopes and the confirmation contract. No filler, though "provider scopes, locks and credits apply" is terse jargon stacking that could be sharper.

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 tool with no output schema, the description covers cost, confirmation, and single-submission execution, which is most of what an agent needs. It omits failure modes (not-found, in-use error), whether deletion is permanent/undoable, and any return/confirmation detail.

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 67%, and the schema itself already documents 'account' and 'confirm' while 'uid' is only constrained by pattern/length. The description only reinforces the confirmation requirement, adding little format or meaning beyond the schema's own descriptions.

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 a specific verb and resource with the exact endpoint ("DELETE /v5/animation_templates/{uid}"), so an agent immediately knows this removes an animation template. It does not explicitly distinguish itself from the other delete siblings (delete_image_template, delete_workflow, delete_webhook), but the named resource disambiguates it in practice.

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 implies usage context ("Current Bannerbear V5 operation") and states that confirmation is mandatory before execution, which guides the confirm parameter. However, it never says when to delete vs. update/leave a template alone, nor any prerequisite about the template being unused, so the guidance is only partial.

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