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

Annotations only declare the safety profile (readOnlyHint=false, openWorldHint=true, destructiveHint=false); the description adds real behavioral context beyond that: external fetch is SSRF-validated, and the import is asynchronous ('enqueued') and bounded. It stops short of saying what the response returns or how duplicates/conflicts on title or slug are handled.

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 no filler; every clause (geospatial dataset, public URL, SSRF, enqueued, bounded) carries distinct 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 mutation with a nested required object, zero schema descriptions, no output schema, and asynchronous execution, the description is too thin: it explains neither the nested payload fields nor what happens after enqueue (job id, status polling), which is critical for correct invocation.

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 schema contains a nested `upload` object with four required subfields (title, slug, collectionSlug, url). The description says nothing about any parameter — not ownerHandle, not the slug pattern constraint, not what collectionSlug refers to — so it fails to compensate for the coverage gap.

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 (import) and resource (geospatial dataset from a public URL), and adds distinguishing traits (SSRF validation, bounded enqueue) that separate it from source_prepare_upload/prepare_download. It does not explicitly name a sibling as the alternative, so it falls short of a 5.

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?

'from a public URL' weakly implies this is the URL-based path versus a direct upload, but the description never names source_prepare_upload as the alternative nor states when not to use it. It also omits that the caller should follow up with source_download_status to poll the enqueued job, leaving the agent to infer the workflow.

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