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

With no annotations, the description carries the full burden of behavioral disclosure. It says only that the tool returns a current temperature via Open-Meteo; it does not disclose that most of the nine parameters appear irrelevant, what happens on invalid city input, whether an external network call is made, or what the response shape looks like.

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, readable sentence with the key action placed up front. It is efficient, though it could be considered under-specified rather than optimally concise given the tool's broader schema.

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 tool has nine optional parameters, no output schema, and no annotations, but the description offers only one narrow use case. It does not explain which parameter to use, how results are returned, or how to handle failures, so an agent lacks enough context to invoke it reliably beyond the simplest case.

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 schema already documents each parameter, including which values are discarded. The description adds no parameter-level meaning beyond 'city,' but because the baseline is 3 for high schema coverage, this is acceptable.

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 and resource: get the current temperature for a city via Open-Meteo. It distinguishes the tool from generic web-check and shape-hint siblings, though the name 'weather-hint' and the broad nine-parameter schema leave some ambiguity about the exact intended scope.

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 about when to use this tool versus siblings such as geo-hint, web-fetch, or fetch-status. No alternatives, exclusions, or selection criteria are mentioned, so an agent must infer usage entirely from the single sentence.

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