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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention side effects, network dependencies, rate limits, response format, or that other schema parameters are ignored or discarded. It only states the core data returned.

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 a single concise sentence that immediately states the tool's purpose and data source. It is front-loaded and has no fluff, though the extreme brevity sacrifices useful operational detail.

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 7-parameter schema, no output schema, and no annotations, the description is insufficiently complete. An agent cannot tell which parameters are actually required, whether the extra parameters are ignored, or what the expected result looks like, making correct invocation rely on guesswork.

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 input schema already gives descriptions for all parameters, so schema coverage is high. The description identifies city as the relevant parameter for the weather lookup, but it does little to clarify the odd mix of extra parameters like ref, url, feed, host, json, and path, nor does it explain that only city matters.

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 the tool returns the current temperature for a city, via Open-Meteo, which makes the fundamental purpose clear. It also differentiates it from sibling hint tools like geo-hint or lib-docs-hint, though it lacks an explicit verb like 'get' or 'fetch'.

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 about when to choose this tool over alternatives, when not to use it, or what conditions select it. The description only implies use when a current city temperature is needed, with no exclusions or comparison to sibling weather-adjacent tools.

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