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 states the tool returns lat/long but does not disclose behavioral traits such as that inputs are discarded, that it calls an external service, or any side effects. The schema mentions 'discarded after the...' for many parameters, but the description does not surface this, leaving behavioral transparency inadequate.

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 concise (a single sentence) and not verbose. However, it lacks structure—no front-loading of key caveats or usage context. It is minimal but not misleading; it earns a middling score for simplicity without offensive verbosity.

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?

The tool has 9 optional parameters and no output schema. The description provides no information about return format, expected city format, or how the parameters map to the geocoding task. It is completely inadequate for an agent to confidently invoke the tool. The mismatch between description and schema makes it nearly unusable.

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?

Though the schema has 100% description coverage, the descriptions are misleading. For example, 'city' is described as 'for a public weather hint; discarded after the call'—not as a place to geocode. Other parameters are entirely unrelated to the tool's stated purpose. The descriptions do not help an agent understand how to construct a valid call, failing to add meaningful semantics 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?

The description states a clear purpose: 'Latitude and longitude for a place via Open-Meteo.' It uses a specific verb and resource. However, the input schema does not align with this purpose; the parameters (e.g., 'ref', 'url', 'host') are unrelated, and the only plausible one, 'city', is described as 'for a public weather hint' not for geocoding. This inconsistency weakens clarity and does not distinguish the tool from siblings like 'weather-hint'.

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. The description merely states what it does, without mentioning any applicable scenario, constraints, or alternative tools. The presence of sibling 'weather-hint' suggests a potential overlap, but no differentiation is given.

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