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

No annotations are provided, so the description must carry the transparency burden. While the read-only nature of a weather tool is implied, the description does not explicitly state side effects, permissions, or that it only reads data. The presence of parameters like 'discarded' and 'no disk access' hints at non-destructive behavior but is not consolidated.

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, which is concise. However, it omits critical information about the parameter set, making the structure feel underdeveloped. It is not front-loaded with the most relevant details beyond the basic purpose.

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?

Given the 9 parameters, many of which are unrelated to weather, the description is incomplete. It does not explain why these parameters exist, how they are used, or what the tool actually does beyond a simple temperature lookup. The description fails to provide sufficient context for an agent to understand the full behavior of 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?

The schema provides descriptions for all 9 parameters, but they are generic and appear to be copy-pasted from other tools (e.g., 'Git ref name; discarded after the shape check'). Only the 'city' parameter aligns with the tool's stated purpose. The parameter descriptions do not coherently explain how they relate to fetching weather data.

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 primary function: 'Current temperature for a city via Open-Meteo.' However, the input schema includes many unrelated parameters (ref, url, feed, host, json, path, zone, query) that are not mentioned in the description, creating confusion about the tool's actual scope.

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 provides no guidance on when to use this tool versus alternatives. It does not mention any conditions, prerequisites, or scenarios where weather-hint is preferred over other sibling tools.

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