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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only adds 'via Open-Meteo,' which signals an external dependency, but omits error behavior, rate limits, return format, and how the tool behaves with the many non-geocoding parameters. The schema's own notes (e.g., 'discarded after the call', 'no disk access') are not in the description, leaving behavioral context thin.

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?

A single, efficient sentence with zero filler and the core fact (lat/long via Open-Meteo) stated up front. The brevity is a strength, though it veers into under-specification rather than deliberate conciseness.

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?

For a tool with 9 parameters, no output schema, and no annotations, a one-line description is grossly inadequate. It neither explains how the parameters relate to the stated purpose nor describes the return value or failure modes, leaving an agent unable to confidently select or invoke it.

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%, which normally sets a baseline of 3. However, the description does not map any of the 9 parameters to its stated purpose, and it actively conflicts with them: a geocoding tool would not need 'url', 'json', or 'path'. The description fails to clarify which parameter (city? query?) actually triggers the lat/long lookup, so it adds no semantic value beyond the schema and creates ambiguity.

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 verb (provide lat/long) and resource (a place via Open-Meteo), but it conflicts with the tool's actual parameter surface. The schema exposes 9 parameters (ref, url, feed, host, json, path, zone) that have nothing to do with geocoding, and only 'city' and 'query' plausibly relate to a place lookup. An agent reading the schema cannot reconcile the stated geocoding purpose with the majority of parameters, so the stated purpose is misleading rather than clarifying.

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 on when to use this tool versus its siblings. Siblings include weather-hint, timezone, iana-zones, and normalize-url, yet the description gives no exclusions or conditions, leaving an agent to guess which tool handles geocoding vs. weather vs. timezone lookups.

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