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

No annotations are provided, and the description does not disclose whether the tool is read-only, what data it returns, or if it has side effects. It implies a safe lookup, but the behavior is not explicitly stated.

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 concise sentence, but it omits necessary context about the parameter set. It is not overly verbose, yet the brevity does not compensate for the missing explanation of the unrelated parameters.

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 complexity and apparent mismatch of the nine parameters, the description fails to provide sufficient context. It does not explain why 'ref', 'url', 'feed', etc. are present, nor does it clarify the intended usage, making the tool confusing and incomplete for an agent.

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?

While schema coverage is 100%, the parameter descriptions are generic and unrelated to the declared weather purpose (e.g., 'Git ref name; discarded after the shape check' and 'Search text; discarded after the length check'). The description only mentions 'city', leaving the other eight parameters unexplained and their roles unclear.

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 'Current temperature for a city via Open-Meteo', which clearly identifies a retrieval action for weather data. However, the broad input schema naming many unrelated parameters (ref, url, feed, host, json, path, zone, query) introduces ambiguity 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 does not explain when to use this tool versus alternatives, nor does it mention any prerequisites or exclusions. It lacks guidance on the intended invocation context or how to select this among the 24 sibling tools.

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