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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a read-only external lookup, but does not clarify that only the city parameter is used, that other parameters are ignored, whether an API key or network access is needed, or what happens for unknown cities.

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, focused sentence with no filler. It front-loads the core purpose and source efficiently.

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 has nine optional parameters, no output schema, and no annotations, yet the description only covers the basic weather lookup. Missing details include which parameter to pass, expected output format (e.g., units), behavior when unrelated parameters are present, and error handling for invalid city names.

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?

Schema description coverage is 100%, so the schema already explains each parameter individually. The description adds no insight into which parameter is relevant for weather lookup, though 'city' is the obvious match. This meets the baseline but does not compensate for the confusing abundance of unrelated optional parameters.

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 provides 'current temperature for a city via Open-Meteo', which gives a specific resource and data source. It does not explicitly distinguish it from sibling tools like geo-hint, but the weather focus is unambiguous enough for basic selection.

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 given about when to use this tool versus geo-hint, lib-docs-hint, or other sibling tools. It also does not explain which parameter to provide or what happens if multiple parameters are supplied.

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