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

No annotations are provided, so the description carries the full burden. It mentions 'via Open-Meteo', implying an external API call, but does not disclose rate limits, error handling, network requirements, or what happens if the place is not found. It also does not explain why many parameters are 'discarded after the call', which is behaviorally puzzling. Minimal disclosure beyond the bare function.

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, which is structurally efficient. However, it is too terse to be useful, omitting essential guidance on parameter usage and output. It is not overly verbose, but under-specification is not the same as conciseness; a 3 reflects the brevity balanced against the lack of necessary detail.

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?

Given the complexity of nine optional parameters with no required fields and no output schema, the description is severely incomplete. It does not explain which parameter identifies the place, what the output format looks like, or provide any examples. An agent cannot reliably invoke this tool based solely on the provided information.

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%, but the parameter descriptions are largely unrelated to geocoding (e.g., Git ref, URL, JSON text). The tool description does not clarify how any parameter maps to a 'place'. Since the schema descriptions are not helpful for the intended purpose, the description should compensate but does not, leaving the agent unsure which parameter to 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 states the core function clearly: 'Latitude and longitude for a place via Open-Meteo.' This gives a specific verb and resource, but it fails to specify how the place is identified among the nine parameters. The purpose is understandable at a high level, but the mismatch between the description and the parameter schema creates ambiguity, preventing a higher score.

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?

There is no guidance on when to use this tool versus the many sibling tools (weather-hint, timezone, normalize-url, etc.). No context is given about typical use cases, prerequisites, or exclusions. The description provides no hint about which parameter to supply or what distinguishes geo-hint from alternatives.

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