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

With no annotations provided, the description must fully disclose behavior. It only states the data source (Open-Meteo) and the output (current temperature), but says nothing about network dependencies, rate limits, error handling, or what happens with non-city parameters. The behavior for other inputs is completely undisclosed.

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 that is efficient and easy to parse. However, it is under-specified, missing critical details. Conciseness itself is good, but the structure could include more context without becoming verbose.

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?

For a tool with nine parameters, no output schema, and no annotations, a one-sentence description is grossly inadequate. It does not explain return format, how to construct calls, or which parameters are relevant for weather. An agent cannot reliably invoke this tool correctly based on the description alone.

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 all nine parameters have descriptive text. The description adds nothing beyond what the schema already provides; it does not clarify how the various parameters relate to the stated weather purpose. Baseline 3 is appropriate since the schema handles parameter documentation.

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 primary function: getting current temperature for a city via Open-Meteo. However, the input schema includes eight additional parameters (ref, url, json, path, zone, query, etc.) that are not mentioned, creating ambiguity about whether the tool serves other purposes. This mismatch reduces clarity for an agent trying to understand when to use it.

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 its siblings (geo-hint, lib-docs-hint, etc.). It does not mention alternatives, conditions, or exclusion criteria, leaving the agent to guess the tool's scope among a large set of similar 'hint' utilities.

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