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

With no annotations, the description carries the full burden. It mentions using Open-Meteo, implying an external network call, but does not disclose how non-city parameters are handled, what happens for missing or invalid city values, or what the response 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 focused sentence with no fluff, and the key information (weather, city, data source) is front-loaded.

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 a 9-parameter schema, no output schema, and no annotations, the description is too sparse. It does not explain the role of the extra parameters, expected output units or format, error behavior, or provide enough context to call the tool correctly beyond guessing that 'city' is the input.

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?

Although every parameter has a schema description, most are irrelevant or copied from other tool contexts (ref, url, feed, host, json, path, zone, query). The tool description only clarifies 'city', leaving the other eight optional parameters unexplained in relation to weather-hint.

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 tool returns the current temperature for a city via Open-Meteo, which is clear and distinguishes it from sibling tools like geo-hint or timezone. It lacks an explicit verb like 'Returns', but the intent is unambiguous.

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 given about when to prefer this tool over alternatives, and the schema contains many seemingly unrelated optional parameters. The agent is left to infer that only 'city' should be used, with no explanation of the other parameters.

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