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

The description does not disclose that only the 'city' parameter is likely used while others are ignored, nor does it mention that a network call to an external service (Open-Meteo) is made. With no annotations provided, the description carries full responsibility for transparency and falls short.

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, clear sentence with no filler. It is well-structured and immediately communicates the core functionality without unnecessary 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 description is too sparse given the tool's complexity. It does not specify the output format, error behavior, or which parameters are actually required. With nine optional parameters and no output schema, an agent lacks essential context to use the tool confidently.

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 the schema covers 100% of parameters, most descriptions are irrelevant to weather (e.g., 'ref' as a Git ref name, 'url' for normalization). Only 'city' aligns with the tool's purpose. This mismatch misleads the agent about which parameters matter and what the tool actually does.

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 tool's primary function: returning the current temperature for a city via Open-Meteo. However, the presence of many unrelated parameters in the schema could confuse an agent about the tool's actual scope, though the core purpose is still evident.

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 mention when to use this tool versus its many sibling tools, nor does it indicate any prerequisites, limitations, or typical scenarios. An agent is left without any direction on invocation.

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