Create image

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

Beyond the annotations (destructive=true, openWorld=true, non-idempotent), the description adds real context: provider scopes/locks/credits apply, a mandatory confirmation step precedes execution, and only one submission is permitted. These are meaningful operational disclosures not derivable from structured fields, though the consequence of failure or reuse is not spelled out.

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 terse fragments, front-loaded with the endpoint and followed by the highest-value constraints. Nothing is wasted, though the fragmentary style makes it slightly less readable than a single clear sentence.

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 costly, non-idempotent, credit-consuming mutation with a very large schema, the safety essentials (confirmation, one submission, credits) are covered and annotations carry the destructive profile. However, the core question of what the tool produces and how template/modifications drive output is left entirely to the schema.

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 account, confirm, payload, and payload_file, establishing a baseline of 3. The description's mention of 'mandatory confirmation' loosely reinforces the confirm parameter but adds no new syntax or format meaning.

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 an HTTP endpoint ('POST /v5/images') rather than a plain-language verb+resource; the actual purpose (create/render an image from a template) must be inferred from the title. It names it as a 'Current Bannerbear V5 operation' but gives no differentiation from siblings like generate_ai_image, preview_render_batch, or create_image_template.

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 operational constraints ('Mandatory confirmation before provider execution; one submission only') but provides no guidance on when to use this tool versus alternatives such as preview_operation, generate_ai_image, or create_batch. No when/when-not conditions or prerequisites for selection are given.

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