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

The description discloses no behavioral traits—no statement about read-only nature, network calls, or side effects. Since there are no annotations, the description carries the full burden, and it fails. Moreover, the parameter descriptions are misleading (e.g., 'ref' is described as 'Git ref name; discarded after the shape check'), suggesting the tool performs arbitrary validation checks unrelated to weather, further obscuring actual behavior.

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 itself is concise—one clear sentence. However, the overall structure is poor because the input schema is cluttered with 9 parameters, most of which are irrelevant to the tool's purpose. The description does not help organize or prioritize these parameters, so while the text is brief, the structure as a whole is confusing.

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 complexity of 9 optional parameters and no output schema, the description is severely incomplete. It does not explain which parameters are essential, how they are used, or what the response looks like. The agent is left without any guidance on how to invoke the tool correctly, especially since most parameters appear to be irrelevant carryovers from other tools.

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 has 100% coverage, but the descriptions are largely irrelevant and copied from other tools (e.g., 'url' as 'HTTPS URL to normalize or cite', 'json' as 'JSON text to validate'). Only 'city' and 'zone' have any plausible relevance, but even these are vague ('City name for a public weather hint; discarded after the call'). The description adds no clarification about which parameters are actually used or how they affect the weather query, providing minimal semantic value and actively misleading 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 clearly states the tool's function: obtaining the current temperature for a city via Open-Meteo. It uses a specific verb ('Current temperature') and identifies the resource ('a city via Open-Meteo'). However, it does not specify the output format or distinguish it from sibling tools, which are mostly about URL checks, math, and other utilities, so it loses a point for not being more explicit about its scope.

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 provides no guidance on when to use this tool versus alternatives. There is no mention of scenarios where weather data is needed, nor any comparison with sibling tools. The only hint is the tool name 'weather-hint,' but the description itself offers no usage context.

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