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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safe-read profile is covered. The description adds useful context that this reveals readiness of an asynchronous format conversion and issues a fresh capability, but it does not say what happens while still pending, whether repeated calls are cheap, or how the capability materializes.

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?

A single front-loaded sentence that leads with the verb 'Poll' and packs the resource, condition, and return into one line. No waste, though the condition ('once conversion is ready') is folded in rather than surfaced as its own cue.

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 carries the full burden of explaining the return, yet only gestures at 'a fresh download capability' without describing the pending state or how readiness is signalled. Combined with zero parameter explanation, it is under-specified for an async polling tool with a nested format/TTL parameter.

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% for two required parameters, one of which is a nested object with an enum of seven export formats and an expiresIn TTL. The description mentions none of this, so it does not compensate for the coverage gap; an agent gets no help on format selection or TTL semantics from the prose.

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 (poll) and resource (a prepared geospatial export), and clarifies the outcome (returning a fresh download capability once conversion is ready). It aligns with the obvious sibling geobble_source_prepare_download, but never names that sibling, so the async hand-off is left implicit rather than differentiated.

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' and the phrase 'once the format conversion is ready' imply this is the status-check step following a prepare call, but there is no explicit when-to-use, no mention of geobble_source_prepare_download, and no guidance on cadence or when to stop polling. Usage is inferable but not stated.

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