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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the core function, but does not mention that most of the 9 parameters are ignored or discarded, nor any rate limits, response format, or side effects. The schema's per-parameter 'discarded' notes partially compensate, but the description itself is silent.

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 sentence with no fluff, making it highly concise. It front-loads the core purpose. However, its brevity borders on under-specification; while it is appropriately short, it omits essential context that would make it genuinely useful.

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 tool has 9 parameters, no required fields, no output schema, and no annotations, the description is severely incomplete. It does not explain which parameters are actually used, what the return value looks like, or how to handle the extraneous parameters. An agent would struggle to call this tool correctly based on the description alone.

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 each parameter has a description. The tool description adds the context that 'city' is the relevant parameter for temperature, which is helpful. However, it does not explicitly state that the other parameters are irrelevant or how they interact, leaving the agent to guess why ref, url, feed, etc. are present. The description adds some meaning but does not fully resolve the mismatch.

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 a specific action ('Current temperature for a city via Open-Meteo') with a concrete resource (city, Open-Meteo). It is unambiguous about the core function, but it does not differentiate from sibling hint tools like geo-hint or lib-docs-hint, which also have specific domains. The wording implies a weather-only tool, but the schema's many unrelated parameters create ambiguity.

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 the many sibling hint tools. The description provides no conditions, prerequisites, or exclusion criteria. An agent cannot infer from this text when to select weather-hint over alternatives like geo-hint or web-fetch.

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