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

Annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false) establish the mutation/safety profile, and the description adds meaningfully by disclosing that exports are 'billed' and asynchronously 'enqueued'. That billing and async behavior is exactly the kind of context annotations cannot express. It stops short of stating auth requirements or how the enqueued job is tracked.

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 with a colon-separated clause structure that wastes nothing. The primary behavior (return capability) precedes the conditional fallback (enqueue billed export), which is the right ordering.

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 mutating, billed, async tool with no output schema and 0% schema coverage, the description covers the key behavioral facts (billing, enqueue, conversion trigger) but omits the structure/meaning of the download object and how to retrieve the enqueued result. Adequate but with clear gaps given the tool's complexity.

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 there are two required parameters, including a nested 'download' object with format and expiresIn fields. The description hints at the format parameter ('requested GIS format') but explains nothing about sourceId or the expiresIn/expiry semantics, leaving the schema to carry the load entirely.

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 (prepare) and resource (dataset download), and uniquely describes the dual-mode outcome: returning a download capability or enqueuing a billed export for format conversion. This clearly separates it from the sibling geobble_source_download_status, though the differentiation is left implicit rather than named.

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 condition that triggers the enqueue path ('when the requested GIS format needs conversion') is stated, implying usage context. However, it never says when to prefer this over geobble_source_download_status for checking results, nor any prerequisites, so guidance is only implied.

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