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

With no annotations, the description carries the full burden. It only says 'via Open-Meteo', implying an external call, but nothing about safety, side effects, or the fact that the schema contains many parameters described as 'discarded' that have no relation to geo. The schema descriptions (e.g., 'Git ref name; discarded') suggest behaviors not disclosed in the description, making it misleading.

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 short sentence, but it is under-specified rather than concise. It omits critical information about parameter usage and behavior, so the brevity is not effective.

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 9 parameters (many irrelevant), no output schema, and no annotations, the description is severely incomplete. It does not state which parameter to use, what the output format is, or any constraints. The tool is impossible to use correctly based on this 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?

Schema coverage is 100%, so the schema documents each parameter, but the descriptions are contradictory or unrelated to geo (e.g., 'ref' for git, 'url' for HTTPS). The tool description adds no clarification about which parameter is the 'place' (likely 'city'), leaving the agent to guess. It fails to compensate for the schema's confusion.

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 verb+resource: returns latitude and longitude for a place via Open-Meteo. However, it does not differentiate from siblings like 'weather-hint' which also likely uses Open-Meteo, and the schema includes many unrelated parameters, muddying the purpose.

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 does not mention any conditions, exclusions, or alternatives, leaving the agent to infer from the vague purpose.

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