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

No annotations are present, so the description carries full behavioral disclosure burden. It does not mention that other input fields are discarded, that an external API call is made, or what the output includes beyond temperature. The main behavior is stated, but key operational traits are omitted.

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?

One short, focused sentence with no filler or repetition. It is front-loaded with the essential fact and is appropriately concise for a simple tool.

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 schema contains eight parameters, most of which are marked as discarded, but the description does not state that city is the only meaningful input for this tool. Without this context, an agent selecting parameters could be misled. No output schema or annotations further compound the incompleteness.

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 input schema already provides descriptions for all parameters, including 'discarded after the call' semantics, so schema coverage is effectively 100%. The description adds little parameter-level meaning beyond implicitly tying 'city' to the tool, which is only a baseline contribution.

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 the core purpose: current temperature for a city, and identifies the data source (Open-Meteo). It is recognizable and distinct from sibling tools like geo-hint, though it lacks an explicit action verb such as 'returns' or 'gets'.

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?

There is no guidance on when to use this tool versus alternatives, no exclusions, and no mention that only the city parameter is relevant. The description simply identifies the provider without giving selection criteria.

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