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

The description explicitly labels the operation 'additive', while the annotations declare destructiveHint: true — the description directly negates the structured safety signal, which is the definition of an annotation contradiction. Otherwise the description is informative (async default, polling, sync host, quota consumption), but the conflict with the annotation creates ambiguity about the tool's risk profile.

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?

Roughly three sentences, front-loaded with the action and the quota caveat, then the async/sync behavior, then the endpoint. Every clause carries information an agent needs; no filler.

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?

With no output schema, the description correctly carries the return-value burden by describing the 'pending' screenshot and the sync alternative, and it notes quota cost. It omits any authentication/prerequisite detail and does not resolve how the destructive annotation should be interpreted, leaving a small gap for an agent deciding whether to invoke it.

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 every parameter (url, width, height, mobile, synchronous, webhook_url) is already documented in the schema, setting the baseline at 3. The description adds operational meaning to 'synchronous' by describing the sync-host/blocking path, but says nothing beyond the schema for the viewport, mobile, or webhook parameters.

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?

States a specific verb + resource ('Capture a screenshot of a web page') and a concrete scope (a public URL), which cleanly separates it from siblings like bannerbear_create_image, bannerbear_create_video, and bannerbear_create_collection. The API endpoint reference reinforces exactly what operation is performed.

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?

Gives explicit operational guidance: async by default with a 'pending' screenshot to poll, or synchronous:true to block for the finished result, plus a warning that the call consumes API quota. That covers the key when/how decision, but it never distinguishes this tool from sibling creation tools (e.g. why screenshot vs. create_image), so no alternatives or exclusions are stated.

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