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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior. The description adds valuable context beyond that: no API key is required, results are nearest first with distances in metres, and calls can take 5–20 seconds on a cold cache. It does not mention rate limits or cache-warming behavior, but the additions are substantive for a read tool.

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?

The description is four dense sentences with no filler. It front-loads the source and availability, then enumerates themes, then gives ordering/distance semantics, and closes with a practical latency note. Every sentence earns its place.

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 the description does not need to explain return values. It covers themes, ordering, distance units, API-key requirements, and latency, which is most of what an agent needs to call this correctly. The only meaningful gap is the undocumented limit parameter and lack of guidance on choosing this tool over siblings.

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 67%, so some parameter meaning is already documented (category, latitude, longitude, radius_m). The description compensates well for the theme enum by explaining what 'places', 'buildings', 'transportation', and 'divisions' each return, including attribute-level detail like building height/floors/area and road geodesic length. It says nothing about the limit parameter, which remains undocumented in both description and schema.

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 and resource ('Open global map data from Overture Maps') and then enumerates exactly what each theme returns: POIs with categories, building footprints with attributes, road/path segments with length, and administrative divisions. An agent can immediately understand this is a feature-retrieval tool rather than a geocoder or routing tool, even though no sibling is named explicitly.

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 description explains what the themes contain but gives no guidance on when to choose this tool over alternatives like geocode, reverse_geocode, or location_report. There are no stated use cases, exclusions, or conditions that would help an agent decide between this and sibling spatial tools.

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