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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It states the operation is a read (get temperature) but does not mention that other parameters are discarded, whether there are rate limits, or what the response format is. The presence of 9 unrelated parameters in the schema without explanation could mislead an agent into thinking they are all relevant.

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, front-loaded sentence with no filler. It is appropriately concise for stating the core purpose. However, given the complexity of a 9-parameter schema, a bit more context about parameter relevance could be added without losing conciseness.

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 description is incomplete for a tool with 9 parameters and no annotations or output schema. It doesn't explain that only 'city' is used, nor does it describe the expected output (units, format). An agent would have to inspect the schema and sibling names to guess that other parameters are irrelevant. Key operational details like network access or error handling are also absent.

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 coverage is 100%, so all parameters have descriptions. The description adds no parameter-level meaning beyond the schema; it merely reiterates the 'city' parameter's role. Since the schema already documents each parameter, the description doesn't compensate for or clarify the parameter usage, leaving the agent to infer 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 clearly states the tool's purpose: retrieving the current temperature for a city via Open-Meteo. It names a specific verb, resource, and data source, which distinguishes it from sibling tools like geo-hint. However, it doesn't clarify that only the 'city' parameter is relevant among the 9 schema parameters, leaving some ambiguity 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?

No guidance is given on when to use this tool versus alternatives. There is no mention of context, prerequisites, or exclusions. The description only states what the tool does, not when an agent should select it over other hint tools.

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