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

With no annotations, the description carries the full burden of disclosing side effects. It does not state that the tool makes a network call to Open-Meteo, whether it is read-only, or what happens with the many parameters described as 'discarded'. The description fails to clarify that only the 'city' parameter is used, leaving behavioral expectations unclear.

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 very concise, consisting of a single sentence. It front-loads the core purpose but sacrifices necessary detail. Given the complexity of the schema (9 parameters) and the lack of output schema, the brevity is not appropriate; it feels under-specified rather than efficiently concise.

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?

This tool is severely incomplete. With 9 optional parameters, no required ones, no output schema, and no annotations, the description does not tell an agent which parameter to use, what the expected output format is, or any behavioral details (e.g., network dependency, error handling). An agent cannot reliably invoke this tool based on the current definition.

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?

While the schema descriptions cover all parameters, they are generic and unrelated to geocoding (e.g., 'url' for normalization, 'json' for validation). The tool description does not explain which parameter(s) to supply for a place, nor does it resolve the ambiguity. An agent would be uncertain whether to use 'city' or any other field, and the description adds no value 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 clearly states the tool returns latitude and longitude for a place via Open-Meteo, which is a specific verb+resource. However, it does not differentiate from sibling tools like weather-hint or iana-zones, and the input schema contains many unrelated parameters (url, feed, json, etc.) that could confuse an agent about the tool's 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?

There is no guidance on when to use this tool versus alternatives. The description does not mention that it is specifically for geocoding, nor does it exclude other uses. No alternatives or conditions are provided, leaving the agent to infer when this tool is appropriate.

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