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

Discloses quota consumption, additive nature, and async behavior (pending collection, polling). Annotations already mark destructiveHint=true; description adds context beyond annotations, no contradictions.

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?

Two concise sentences, front-loaded with key info (verb, resource, quota, async, polling). No filler words.

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?

Explains async lifecycle and polling mechanism despite no output schema. Parameter details are in schema. With sibling tools covering polling and other actions, description is sufficiently complete for a creation tool.

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 coverage is 100%, so description doesn't need to detail parameters. Description does not add new info on parameters beyond the schema, but baseline 3 is appropriate given coverage.

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?

Clearly states 'Generate a collection of images from a template set', specifying verb, resource, and scope. Distinguishes from siblings like bannerbear_create_image (single image) and bannerbear_get_collection (polling) by mentioning async return.

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?

Provides context: tool is for creating a batch from a template set, consumes API quota, and is async requiring polling via bannerbear_get_collection. Implicitly contrasts with single-image creation, but lacks explicit 'when not to use' or alternative selection guidance beyond polling.

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