Subtitle video

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

Annotations already declare a non-read-only, destructive, non-idempotent, open-world operation, and the description reinforces this with 'provider scopes, locks and credits apply' and 'one submission only' — useful additions on cost consumption and non-retryability. It still omits what gets modified/returned and the practical effect of the operation, keeping it short of a 5.

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 short clauses, front-loaded with the endpoint and immediately followed by the operational constraints. Nothing is padded, though the raw URL string is low-value text for an agent compared to a plain-language purpose statement.

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 complex, destructive, credit-consuming video operation with a nested payload and no output schema, the description never explains the resulting artifact (output video/subtitle job), how it is delivered, or job life-cycle. Annotations plus schema cover the surface, but the high-complexity context demands more than endpoint + confirmation boilerplate.

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 account/confirm/payload/payload_file and all nested payload fields are already documented in the schema. The description adds nothing about payload shape or parameter meaning, 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 leads with the HTTP endpoint ('POST /v5/tools/subtitle_video') and calls it a 'Current Bannerbear V5 operation', but never states what the operation actually does to a video (e.g. burns in subtitles/captions). The self-descriptive name carries the meaning, so it is distinguishable from video siblings, but the description itself adds no verb+resource clarity.

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 gives one firm usage constraint — 'Mandatory confirmation before provider execution; one submission only' — which tells the agent to set confirm=true and not retry. However, it offers no guidance on when to choose this tool versus other video tools (trim_video, overlay_video, add_audio, etc.), so routing is left to the name alone.

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