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

No annotations are provided, and the description does not disclose side effects, return behavior, or what happens with the supplied parameters. Several parameter descriptions mention 'discarded' or 'no disk access', but this does not clarify the tool's actual behavior.

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 vague and does not effectively communicate the tool's core function. The lack of structure and essential details makes it less useful despite its brevity.

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?

There is no output schema and no explanation of what the tool returns or how inputs map to outputs. Given the confusing parameter list, the description is insufficient for an agent to correctly invoke the tool.

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 description coverage is 100%, the parameter descriptions are mostly unrelated to the stated purpose. For example, 'ref' is described as a Git ref, 'feed' as an RSS URL, and 'json' as JSON to validate, all of which seem disconnected from returning latitude and longitude for a place.

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 'Latitude and longitude for a place via Open-Meteo', which conveys a rough purpose, but it lacks an explicit verb and does not clarify which input represents the place. The parameter list contains many unrelated fields, further obscuring the tool's actual function.

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 use this tool versus alternatives. The sibling tools include related tools like weather-hint and normalize-url, but no distinctions or selection criteria are provided.

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