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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds the HTTP method/path and states results are GeoJSON features. It omits auth, rate-limit, and error details, but for a read-only external lookup it provides useful behavioral context beyond 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 compact sentences, front-loaded with purpose and return type; the endpoint is supplementary and no sentence is wasted.

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?

With a fully documented schema and readOnly annotation, the description supplies the key missing output context ('GeoJSON features') despite no output schema. It could mention authentication or rate limits, but the essential calling information is present.

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 100%, so all seven parameters, including the limit/types interaction, excludeTypes, worldview, and language, are already documented. The description only restates longitude/latitude order in the endpoint and adds no parameter meaning beyond the 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?

States a specific verb ('Find place(s)'), the exact input resource (longitude/latitude), and the return format. The coordinate-based scope inherently separates it from forward-geocoding siblings such as maptiler_geocode.

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 implies the tool is for coordinate inputs but gives no explicit when-to-use, when-not-to-use, or alternative selection guidance. An agent can infer it replaces forward geocoding when lat/lon are known, but must rely on the name and sibling context.

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