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

readOnlyHint=true already establishes this as a safe read, but the description goes further by disclosing the async lifecycle: status values (pending|completed|failed) and that image_urls populates only on completion. That return-shape behavior is not derivable from the annotation and is exactly what a polling agent needs. It stops short of stating polling cadence or what a failed response contains.

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 compact clauses that front-load the core action and then layer the polling purpose and response shape, plus the raw endpoint. Zero filler sentences; every clause adds usable information.

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 single-parameter read tool with no output schema, the description supplies the otherwise-missing return semantics (status enum, image_urls map, completion condition) and the endpoint. Only minor gaps remain, such as polling frequency or error-case detail.

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?

With one parameter at 100% schema description coverage, the schema already documents uid fully (including its origin in a create_collection response). The description only restates it via the API path '/v2/collections/{uid}', adding no new syntax or format 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?

States a specific verb and resource ('Get a single collection') and immediately distinguishes it from the sibling bannerbear_create_collection by framing it as the polling endpoint for an async render. An agent can tell exactly what this returns without opening any schema.

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?

Explicitly says 'poll this to check an async render', which gives a concrete when-to-use condition tied to the create_collection workflow. No wrong-tool exclusion is named, but there is no competing get-collection-status sibling, so the guidance is sufficient in practice.

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