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

There are no annotations, so the description must carry transparency. It discloses the external Open-Meteo dependency but does not mention side effects, read-only behavior, or data handling; the schema's 'discarded' notes are not in the tool description.

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 with no filler; the core purpose is front-loaded and the Open-Meteo dependency is included.

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 description is too sparse for the actual input schema: nine optional parameters, no output schema, and no annotations. It does not explain which parameter is the place, how to interpret the output, or how to handle the unrelated parameters.

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?

With 100% schema coverage, the baseline is 3, but the description adds no mapping between 'place' and any parameter, and the city parameter description ('public weather hint; discarded') conflicts with the geocoding purpose, leaving the relevant input ambiguous.

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/longitude for a place via Open-Meteo, which distinguishes it from siblings like weather-hint. It lacks an explicit verb and doesn't identify the input parameter, but the core function is understandable.

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 given about when to choose this tool over alternatives; it doesn't mention weather-hint or any other sibling, nor does it state the intended use case beyond the short description.

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