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

With no annotations, the description carries the full burden of behavioral disclosure. It states that the tool provides a temperature via Open-Meteo, but it does not disclose that this is an external network call, what happens if the city is not found, or that most schema parameters appear to be ignored or discarded. The parameter descriptions in the schema hint at discard behavior, but the tool description itself does not.

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, front-loaded sentence with no wasted words. It immediately states the tool's purpose and source. Its brevity is efficient, even if other dimensions suffer from the lack of detail.

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 tool has nine parameters, no required fields, no annotations, and no output schema. The description is too sparse to guide an agent about which parameters are relevant or what the response looks like. The schema helps, but the description does not reduce the confusion caused by a large set of seemingly unrelated parameters like ref, url, feed, host, json, path, zone, and query.

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%, so the baseline is 3. The description adds emphasis on 'city' as the meaningful parameter, which is helpful, but it does not explain the relationship between the other eight schema parameters and the weather functionality. Since the schema already describes each parameter clearly, the description adds little beyond what is structured.

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 identifies the tool's function: retrieving the current temperature for a city via Open-Meteo. It names a specific resource and source, and the tool name weather-hint matches the description. However, it lacks an explicit verb like 'get' or 'retrieve' and does not contrast with sibling tools such as geo-hint.

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?

The description implies a use case—when you need a city's current temperature—but gives no guidance on when to prefer this tool over alternatives like geo-hint or web-fetch. There are no exclusions, prerequisites, or notes about the many other schema parameters and whether they should be provided.

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