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

With no annotations, the description carries the burden of explaining behavior. It mentions 'via Open-Meteo,' implying an external network call, and schema descriptions include phrases like 'discarded after the call' and 'no disk access,' which hint at harmlessness, but side effects, failure modes, and data handling are not explicitly described.

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, so it is concise, but it sacrifices necessary detail. It front-loads the output type but omits the key input requirement, making the sentence less useful than its brevity would suggest.

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 the return format or error behavior. The description does not specify which parameter to provide, how latitude and longitude are formatted, or how the tool interacts with the confusing set of optional parameters, so an agent cannot confidently invoke it.

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 descriptions cover all parameters 100%, the descriptions are largely irrelevant to the stated purpose. Parameters like 'ref', 'url', 'feed', 'host', 'json', 'path', and 'zone' have no clear connection to returning latitude and longitude, and none of the descriptions clearly identifies the input needed to specify 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 says 'Latitude and longitude for a place via Open-Meteo,' which conveys the output type but lacks a clear verb and does not identify which input parameter represents the 'place.' It is not specific enough to distinguish from similar geographic or weather tools.

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 usage guidance is provided. The description does not state when to use this tool instead of siblings like weather-hint, normalize-url, or iana-zones, nor does it explain how to select among the nine unrelated optional parameters.

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