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

No annotations are provided, and the description does not disclose whether the tool makes an external network call, what failure modes exist, or whether other parameters are silently ignored. The parameter descriptions vaguely state that many fields are 'discarded', but this is not integrated into a coherent behavioral picture.

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 main description is a concise one-liner: 'Current temperature for a city via Open-Meteo.' It avoids unnecessary words. The schema itself contains clutter, but the description portion is efficient.

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 lacks expected contextual details: no output schema, no units (e.g., Celsius/Fahrenheit), no example usage, and no error handling notes. The description is too sparse for an agent to know exactly what response to expect or how to handle failures.

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 descriptions are generic and likely copied from other tools (e.g., 'Git ref name; discarded after the shape check', 'JSON text to validate; discarded after the check'). The only plausible relevant parameter, 'city', has a confusing description that says it is 'discarded after the call'. No parameter is marked required, and there are no enums or usage examples.

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 primary action: returning the current temperature for a city via Open-Meteo. It is specific enough to distinguish the tool's core purpose, though it does not explicitly contrast with sibling tools.

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 alternatives. The description does not mention that the 'city' parameter is the only relevant input, nor does it explain how this tool relates to similar sibling tools.

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