open-weather.getCurrentWeather

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

Annotations already communicate readOnly, idempotent, and non-destructive behavior. The description adds no context about how the city is determined, whether a default city is used, or why the schema accepts no parameters despite saying 'for a city'.

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?

A single, front-loaded sentence with no filler. Every word contributes to the basic purpose statement, even though additional clarification is needed elsewhere.

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 is simple and has good annotations plus an output schema, but the description's central omission—how 'a city' is selected when no parameter exists—makes it incomplete for reliable invocation. It also offers no comparison with the closely related getForecast tool.

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?

With zero parameters, the baseline is 4, but the description's phrase 'for a city' implies an input that the schema does not support. It does not clarify that the city must be preconfigured or otherwise resolved by the server, creating real invocation ambiguity.

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 resource and action: 'Get current weather for a city'. It distinguishes from the sibling getForecast via the word 'current', but it leaves ambiguous how the city is supplied given that the input schema has zero parameters.

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?

There is no guidance about when to use this tool versus open-weather.getForecast or any other sibling. The description gives no decision criteria, exclusions, or alternative tool references.

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