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

The description implies a read-only operation (fetching temperature), but it does not disclose side effects, error conditions, rate limits, or the fact that many supplied parameters appear to be ignored. Since no annotations are present, the description bears the full burden and falls short.

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 concise and front-loaded, but the overall tool definition is bloated with nine unrelated optional parameters. The brevity of the description is good, but the surrounding schema structure undermines clarity.

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 definition lacks essential context: no output format is described, the parameter list is almost entirely irrelevant to the stated purpose, and there is no explanation of how the tool handles extraneous inputs. This is far from complete for an agent to confidently invoke the tool.

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 parameter descriptions are contradictory and unhelpful. For example, the 'city' parameter is described as 'discarded after the call,' directly conflicting with the stated purpose, and most other parameters (ref, url, feed, json, path, etc.) have descriptions that suggest they are irrelevant. This actively misleads rather than clarifies.

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 the tool's core purpose: returning the current temperature for a city via Open-Meteo. It names a specific resource and action, but it does not address the many unrelated parameters in the input schema, which could confuse an agent about what the tool actually uses.

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 versus sibling tools, nor which parameters are relevant. The description implies 'city' is important, but all parameters are optional and several are explicitly described as discarded, leaving usage ambiguous.

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