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

With no annotations, the description carries the full burden, but it only states the output without disclosing that most parameters are discarded after checks, that it is a hint (not authoritative), or how it interacts with Open-Meteo. The parameter descriptions hint at varied behaviors, but the main description omits them.

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 with no waste, but it is too brief to be functional. It lacks any structure or elaboration, making it under-specified rather than 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?

For a tool with 9 optional parameters, no output schema, and no annotations, this description is severely inadequate. It does not explain return format, error handling, or how to choose inputs, leaving the agent with virtually no guidance.

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 parameter descriptions themselves are inconsistent with the tool's stated purpose (e.g., 'city' mentions weather hints, 'ref' is a git ref). The main description adds no clarification about which parameter is the primary input or how they combine, so an agent cannot determine correct 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 action ('Latitude and longitude for a place via Open-Meteo') but the tool's 9 unrelated parameters (ref, url, feed, host, json, path, zone, query) conflict with this narrow purpose, making the actual function ambiguous. It does not distinguish from siblings like weather-hint or timezone.

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 on when to use this tool versus alternatives like weather-hint, timezone, or iana-zones. There is no mention of conditions, prerequisites, or which parameter to supply for a given use case.

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