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

No annotations are provided, so the description must carry the full behavioral burden. It mentions the Open-Meteo external service but does not disclose whether this is a safe read-only operation, how failures are surfaced, what output shape to expect, or why several input parameters are described as discarded. This is insufficient for a tool with no annotations.

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 one short, front-loaded sentence with no filler: 'Current temperature for a city via Open-Meteo.' It efficiently communicates the core purpose.

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 messy multi-parameter schema, no annotations, and no output schema, the one-sentence description is not enough for an agent to invoke the tool correctly. It does not clarify parameter selection, output format, error behavior, or the expected temperature unit.

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 schema contains many unrelated parameters (ref, url, feed, host, json, path) and a required field 'test-default-value' that is not defined in properties. The description does not clarify that only 'city' matters and the rest should be ignored. While each property has a schema description, the confusing and contradictory schema undermines parameter semantics, and the description adds no rescue.

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 a concrete outcome: 'Current temperature for a city via Open-Meteo.' It names the verb/result (current temperature), the target (city), and the data source (Open-Meteo), which distinguishes it from vague sibling 'hint' tools like geo-hint or lib-docs-hint. It does not explicitly contrast with siblings, but the weather-specific output is enough for basic purpose clarity.

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?

The description gives no guidance on when to use this tool instead of alternatives, nor any exclusion criteria. It also fails to tell the agent that, despite many schema fields, only 'city' is relevant. With many sibling '-hint' tools, this is a real gap.

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