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

No annotations are provided, and the description does not disclose side effects, external calls beyond mentioning Open-Meteo, error behavior, rate limits, or whether it is read-only. The lack of any behavioral detail leaves the agent guessing about operational implications.

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 extremely short and contains no filler words, making it concise. However, it is too brief to provide necessary context, though this is a separate issue from wordiness. Structurally, it front-loads the key information.

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 schema has 9 parameters and no output schema, the description is grossly incomplete. It fails to explain the role of the extra parameters, what the tool returns, how to interpret results, or any constraints. The agent has insufficient information to use the tool correctly.

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?

While the input schema has descriptions for all 9 parameters, they are entirely unrelated to the stated purpose of a weather hint (e.g., 'Git ref name', 'HTTPS URL to normalize or cite'). The description does not explain how these parameters relate to fetching current temperature, making them misleading and causing confusion for the agent.

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 'Current temperature for a city via Open-Meteo,' which conveys the core resource and scope but lacks an explicit verb and does not differentiate from sibling tools like geo-hint or timezone. It is clear in a minimal sense, but the mismatch with the extensive input schema undermines 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?

There is no guidance on when to use this tool versus any alternative. The description does not mention any conditions, prerequisites, or typical scenarios, leaving the agent without direction.

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