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

Annotations already mark this as a write (readOnlyHint=false), open-world (openWorldHint=true), and non-destructive operation. The description adds genuinely new behavioral facts beyond the annotations: SSRF validation of the URL, the enqueue (async) nature, and a bounded import limit. It stops short of explaining how to poll the enqueued job or cancel it.

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 communicates the action, target, and key behavioral traits with no filler. Sized appropriately for the amount of information conveyed.

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?

Given the mutation semantics, nested object, 0% schema descriptions, and no output schema, the description is only partially complete. It discloses SSRF and the enqueue but omits any parameter meaning and any pointer to how the resulting async job is tracked or cancelled.

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 description says nothing about ownerHandle or the nested upload fields (title, slug, collectionSlug, url, description). For a tool with a nested object, the schema supplies only constraints (patterns, lengths) and no meaning, so the description 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?

The description states a specific verb ('Import') and resource ('a geospatial dataset from a public URL'), which cleanly separates it from read-side siblings like geobble_source_download_status. It does not, however, name any sibling or explain how it differs from geobble_source_prepare_upload or geobble_project_submit_dataset_request, so the distinction must be inferred from the name.

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?

There is no explicit when-to-use guidance and no mention of alternatives, prerequisites, or the fact that the import is asynchronous. The single hint, 'public URL', implies a precondition but leaves the agent to infer the rest.

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