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

No annotations are provided, and the schema descriptions introduce contradictory behavior hints ('discarded after the shape check', 'discarded after the call') that conflict with the stated purpose of returning coordinates. The external Open-Meteo dependency is mentioned but failure modes, rate limits, or side effects are not disclosed.

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 a single concise sentence. However, the schema's parameter set is large and disorganized, detracting from the overall structural clarity.

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 9 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain the response format, which parameter drives the lookup, how errors are reported, or why unrelated parameters exist.

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?

All 9 parameters have descriptions (100% coverage), but most are clearly mismatched with the geocoding purpose — ref, url, feed, host, json, and path appear copied from unrelated tools. Only city and query plausibly relate to geocoding, leaving the agent uncertain which parameter to actually use.

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 clearly states the tool returns latitude and longitude for a place using Open-Meteo, which distinguishes it from siblings like weather-hint. However, it lacks an explicit verb and the schema parameters (ref, url, feed, etc.) create confusion about the actual scope.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention that city or query should be used for geocoding, nor does it cross-reference related tools like weather-hint or iana-zones.

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