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 discloses that the tool returns latitude and longitude, but nothing else: no side effects, no input handling (despite schema notes about discarding values), no error behavior, and no indication of whether it is read-only. This minimal transparency is insufficient for a tool with no annotation safety profile.

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 sentence that is front-loaded with the core function. It is efficient and wastes no words. While it may be too brief for the tool's complexity, that is more a completeness issue than a conciseness issue, 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?

Given the tool has 9 optional parameters, no required fields, no output schema, and no annotations, the description is grossly incomplete. It does not specify which parameters are needed to obtain coordinates, how they are combined, what the response format is, or any constraints. An agent cannot confidently invoke this tool based solely on the description.

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% (all 9 parameters have descriptions), so the baseline is 3. The tool description itself adds no meaning beyond the schema, and it creates ambiguity about which parameter specifies the 'place' (e.g., city vs. query). However, since the schema already documents each parameter, the description does not need to compensate heavily, but it also fails to clarify usage.

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: returning latitude and longitude for a place, using Open-Meteo. This is a specific verb+resource and distinguishes it from siblings like weather-hint (which likely provides weather data). However, it does not explicitly differentiate from other location-related tools, but the intent is 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, nor any exclusions or conditions. The description only states what it does, not the context in which it should be chosen. This leaves the agent to guess which sibling (e.g., weather-hint) might be more appropriate.

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