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

With no annotations present, the description carries the full burden of behavioral disclosure. It only mentions the happy-path result (current temperature) and does not disclose that most of the 9 input parameters are discarded, that it is a network-backed public API call, or any side effects/limitations.

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?

A single, front-loaded sentence with zero fluff. It communicates the core purpose in eight words and is perfectly scannable.

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?

Despite the simple one-liner, the tool has a surprising 9-parameter schema with many 'discarded' fields, and no output schema is provided. The description does not explain which parameters to use, that most are ignored, or what the return payload looks like. An agent could not confidently invoke this tool correctly without further investigation.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds only that 'city' is the relevant parameter, but it does not help the agent understand that the other eight parameters are irrelevant for the weather call. The schema itself already explains those parameters, so the description neither harms nor significantly helps.

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 a specific verb ('Current temperature'), a clear resource (a city), and the data source (Open-Meteo). It is immediately clear what weather-hint does and is distinguishable from sibling 'hint' tools like geo-hint or lib-docs-hint.

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 instead of alternatives, nor about prerequisites like city name format or API availability. The description only states the function, leaving usage context entirely to inference.

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