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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that the tool returns lat/lon for a place, but does not disclose that many input parameters are discarded, whether the call is read-only, involves network requests, or what side effects occur. The schema hints at discarding parameters but the tool description omits this entirely.

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 that front-loads the core function. However, it is too brief given the complexity of the schema and does not structure information about parameter usage or behavior. It is efficient but under-specified, so a score of 4 is appropriate.

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 annotations, and no output schema, the description is severely incomplete. It does not explain the return format, which parameters are relevant, or how to handle the seemingly unrelated fields. The tool cannot be called correctly based on the description alone.

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?

Although schema coverage is 100%, the descriptions of the parameters do not align with the tool's stated purpose. For example, 'city' is described as for a 'public weather hint' and 'discarded after the call', which conflicts with geocoding. The description adds no clarity about which parameter to use for the place, making it hard for an agent to select the correct input.

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 primary function: providing latitude/longitude via Open-Meteo. However, the input schema contains nine parameters, many of which (ref, url, feed, host, json, path, zone, query) seem unrelated to geocoding, creating ambiguity about what the tool actually does. The description does not address this mismatch, so the purpose is only partially clear.

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 alternatives like weather-hint, timezone, or iana-zones. No conditions, prerequisites, or exclusions are mentioned. The agent is left to infer usage from the schema, which is confusing given the unrelated parameters.

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