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 mentions 'via Open-Meteo,' implying an external API call, but does not disclose that most of the 9 schema parameters are discarded, that only city is truly relevant, or any failure/rate-limit behavior. The schema already hints at discarded parameters, but the description adds little behavioral context.

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, direct sentence with no filler. It front-loads the core purpose. However, given the tool's 9-parameter schema, a bit more structure (e.g., noting that only city is used) would make the sentence more helpful without sacrificing 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 tool has 9 parameters, no annotations, and no output schema, yet the description is only one sentence. It does not explain the role of the other parameters, what input an agent should supply, or what the return value looks like. An agent seeing the broad schema could easily be confused about whether to pass url, path, or city. The description is under-specified for the tool's actual complexity.

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 baseline is 3. The description adds minimal parameter semantics: it implies the city parameter is key, but the schema already says 'City name for a public weather hint.' It does not clarify how the other parameters relate to the weather functionality beyond what their own descriptions already state.

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 a specific verb and resource: 'Current temperature for a city via Open-Meteo.' This clearly differentiates the tool from siblings like geo-hint or lib-docs-hint and tells an agent exactly what the tool returns.

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 provided about when to use this tool versus alternatives. It does not mention exclusions or conditions that would route an agent to a sibling tool, so the agent must infer usage solely from the purpose statement.

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