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

No annotations are available, so the description carries the entire burden for behavioral disclosure. It only says 'Current temperature via Open-Meteo', implying a read-only query, but it does not state side effects, error behavior, data handling, or that all parameters except city are discarded. This leaves significant unknown behavior.

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, efficient sentence: 'Current temperature for a city via Open-Meteo.' It packs the core action, subject, and source with no unnecessary words.

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 there are nine input parameters, no output schema, and no annotations, the description is incomplete. It does not specify return format, units, behavior for invalid city, or the purpose of the other eight schema fields. An agent cannot confidently invoke this tool or interpret its results solely from this description.

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% for all nine parameters, so the schema already explains each field. The description adds only that the city field is relevant, but it does not explain how the tool should treat the other eight parameters, nor does it add any semantic value beyond what is already in the schema.

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 action and resource: get current temperature for a city via Open-Meteo. This clearly identifies the weather lookup purpose and distinguishes it from sibling tools like geo-hint or timezone, though it does not explicitly name any alternatives.

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 on when to use this tool versus alternatives. The description simply states what the tool does, leaving the agent to infer appropriate invocation context without mention of criteria, prerequisites, or related tools.

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