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

There are no annotations and the description only says it returns current temperature; it does not disclose whether it makes a network call, what happens with no parameters, or whether any inputs are ignored despite several descriptions saying 'discarded.'

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 main description is concise and front-loaded, but the tool definition includes a large schema with irrelevant parameters and repetitive 'discarded' notes, adding unnecessary clutter.

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 does not explain the expected output format, units, error behavior, or which parameters are used; with no output schema and no usage guidance, the tool is not fully contextualized.

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?

Most parameter descriptions are unrelated to weather (Git ref, URL, RSS feed, JSON, query), and the only relevant one, city, is described as 'discarded after the call,' which is confusing and undermines its semantic usefulness.

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 one-sentence description states the core purpose (current temperature for a city via Open-Meteo), but the input schema introduces nine unrelated optional parameters and no required city field, making it unclear which input actually drives the tool.

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 about when to use this tool versus siblings such as geo-hint or timezone, nor any indication of prerequisites or expected invocation patterns.

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