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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds that it blocks/delays until 'the PNG is rendered' and yields a 'download capability', which is useful behavioral context, but it omits pending/failed states and whether the returned download link expires.

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?

One tightly written sentence with the polling action and the success condition front-loaded; nothing is wasted. It is arguably too terse for the state machine it implies, but structurally it is clean.

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?

There is no output schema, so the description carries the burden of describing the response, and it only gestures at it ('a download capability'). The intermediate not-yet-ready and failure outcomes an agent will actually encounter while polling are left undocumented.

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 0% and the single required parameter (exportId) is never explained in the description. The schema only gives format/pattern, not provenance or meaning, so the description fails to add the missing semantics (e.g., 'the UUID returned by geobble_map_image_export_prepare').

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 pairs a specific verb ('Poll') with a specific resource ('map image export') and states the outcome ('return a download capability once the PNG is rendered'). It is clearly distinguishable from geobble_map_image_export_prepare, though it never names that sibling as its predecessor.

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?

The word 'Poll' implies repeated invocation until the image is ready, but there is no explicit guidance on when to call it, how often to poll, what to do while not ready, or that the exportId must come from geobble_map_image_export_prepare. No alternatives or exclusions are named.

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