get-weather-forecast

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

Discloses the time range (today + 3 days) and data source (Gaode map). However, no annotations are provided, and the description does not mention other behavioral traits such as update frequency, units, or error handling. With no annotations, the description carries the full burden but only partially fulfills it.

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?

Extremely concise: two short sentences that front-load the main purpose and scope. Every word adds value; no redundancy or filler.

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 simple tool with one parameter and no output schema, the description covers the essential aspects: input format, output time range, and data source. It is nearly complete, though lacking details on output structure or error conditions. Given the tool's low complexity, this is adequate.

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%, and the description's mention of city name or adcode matches the schema's own description. The description adds no new semantic information beyond what the schema already provides, so a baseline score of 3 is appropriate.

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?

Clearly states the tool retrieves a weather forecast for a specified city, including today and next 3 days, using Gaode map data. The name and description effectively distinguish it from the sibling 'get-weather-live' (current weather).

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?

Mentions acceptable input formats (city name or 6-digit adcode) but provides no explicit guidance on when to use this tool versus 'get-weather-live'. The distinction is implied by 'forecast' vs 'live' but not explicitly stated.

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