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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds that results come back as GeoJSON features and names the underlying GET endpoint, but discloses nothing about auth requirements, rate limits, or result ordering. Moderate added value over annotations.

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 tight sentences with no filler; the core purpose is front-loaded and the API detail is secondary. Every clause carries 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?

There is no output schema, so the description usefully notes the GeoJSON feature return shape. With full schema coverage and a read-only annotation, this is nearly complete, though it omits any mention of auth, limits, or the worldview/type filtering behavior.

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 100%, so every parameter (limit, types, language, lat/long bounds, worldview, excludeTypes) is already documented in the schema. The description adds no parameter-level meaning beyond reiterating longitude/latitude, matching the baseline when the schema does the heavy lifting.

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 and resource ('Find the place(s) at a given longitude/latitude'), which clearly distinguishes reverse geocoding from the forward-geocoding sibling maptiler_geocode. It stops short of explicitly naming the sibling or stating the contrast, so it is clear but not fully differentiated.

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 'place at coordinates' framing implies the use case (turn a lat/long into a place), and the API line signals this is a lookup call. However, there is no explicit when-to-use, when-not, or reference to alternatives such as maptiler_geocode or maptiler_batch_geocode.

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