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

The description only states the high-level function. It does not disclose whether the tool performs a network request, whether it is read-only, any side effects, or what inputs are needed. Given no annotations exist, this is insufficient for full transparency.

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 with no superfluous words. It follows a clear pattern: 'Current temperature for a city via Open-Meteo.'

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 large number of unrelated parameters and no required fields, the description and schema do not provide enough context for an agent to confidently invoke the tool. There is no indication of what a typical call looks like or whether 'city' is required.

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 includes 9 parameters, but only 'city' is plausibly relevant to weather; others like 'url', 'feed', and 'json' appear copied from other tools. The parameter descriptions are generic and some say 'discarded after the call', which is confusing. The description does not clarify which parameters are required or optional.

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 function: 'Current temperature for a city via Open-Meteo.' This is a specific verb-resource pairing that distinguishes it from sibling tools like 'calc-eval' or 'fetch-status'.

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 guidance is provided on when to use this tool versus alternatives. The description simply states the function without mentioning any conditions, alternatives, or exclusions, leaving the agent to guess.

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