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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds real context beyond that: the backing provider (Nominatim) and the existence of a geospark.warnings signal for ambiguous names, which an agent would not know from structured fields.

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?

Two short sentences with the core purpose front-loaded and the ambiguity handling following. The odd indentation/whitespace from formatting is cosmetic and wastes no semantic content.

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?

An output schema exists, so return values needn't be explained, and the ambiguity workflow is covered. Still missing: meaning of limit, whether multiple candidates are returned by default, and any hint that this hits an external service (latency/rate considerations).

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 coverage is 50%: query is documented there, but limit has only type/default/bounds and no explanation. The description partially compensates by implying the query string format and suggesting adding a region to disambiguate, but says nothing about limit or how many results to expect.

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+resource: 'Find coordinates for an address or place name', plus the data source (Nominatim). This implicitly distinguishes it from the sibling reverse_geocode (which goes coords→place), though the contrast is never made explicit.

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?

Gives actionable guidance for the ambiguous-name case (check geospark.warnings, ask the user, or add a region), which is genuinely useful. However, it never says when to prefer this over reverse_geocode or location_report, so tool selection among siblings is left to inference.

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