get_weather

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

No annotations are provided, so the description carries the full burden. It does not mention that the operation is read-only, nor does it describe potential side effects, output format, or error behavior. This lack of detail means an agent cannot anticipate the tool's full impact.

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 concise, consisting of two sentences that directly convey the purpose and parameter constraints without unnecessary detail or repetition. It is well-structured and easy to parse.

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 covers the essential context for making a request (what the tool does, what inputs it accepts). It does not specify the output format or any response details, but given that no output schema is defined and the tool is a simple retrieval, this is a minor gap.

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?

The schema provides only types and titles, but the description adds meaningful semantics: location is a city, region, or country with examples, and forecast_days is an integer between 1 and 7. This fully clarifies both parameters' intended usage.

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 ('get') and clearly identifies the resource ('current conditions and a weather forecast for a place'). It also provides examples for the location parameter, removing ambiguity about what kind of place is accepted.

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 gives concrete guidance on parameter values (forecast_days range 1-7, location format) and implicitly indicates the tool is for retrieving weather data. However, it does not explicitly state when to use it versus alternatives, though no sibling tools are listed.

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