Add audio

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true. The description adds genuine context beyond these: 'provider scopes, locks and credits apply', mandatory confirmation before provider execution, and that only one submission is allowed. It still omits what is destroyed or the return 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?

The first sentence is pure boilerplate (endpoint restatement plus 'Current Bannerbear V5 operation'), and the confirmation/single-submission notes are generic wording reused across tools. Space is spent on filler rather than front-loading the tool's actual effect.

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, open-world tool with a nested payload object and no output schema, the definition leaves the core operation unexplained. An agent cannot learn what adding audio does or its side effects from this text.

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 100%, so the schema already documents all four parameters and the nested payload fields. The description adds no parameter-level detail (e.g., how 'mode' or 'volume' behave), so the baseline 3 applies.

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 restates the endpoint 'POST /v5/tools/add_audio' and calls it a 'Current Bannerbear V5 operation', which is essentially a tautology of the tool name. It never states the actual resource/action (adding an audio track to a video) nor differentiates it from siblings like overlay_video or subtitle_video.

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 notes mandatory confirmation and 'one submission only', which hint at preconditions, but gives no guidance on when to choose this tool over the many sibling video operations. No alternatives or when-not-to-use conditions are provided.

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