get_weekly_forecast

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 discloses the key behavioral trait: free tier returns 3 days. This adds value beyond the schema. It does not contradict any annotations (none present).

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 sentence with no extraneous words. It front-loads the purpose and scope, making it efficient for agents 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 omits details about the output format (e.g., temperature, precipitation, dates). Since there is no output schema, the description should ideally mention what fields are returned to fully guide an agent.

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 coverage is 100% as both 'lng' and 'lat' have descriptions. The tool description adds no further parameter semantics, but the schema adequately documents them. Baseline 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?

The description clearly identifies the verb 'get', resource 'daily weather forecast', and scope 'up to 7 days (free tier returns 3 days)'. This distinctively separates it from siblings like get_hourly_forecast (hourly) and get_historical_weather (historical).

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 provides usage context by noting the free tier limitation (3 days vs 7), which helps agents decide when to use this tool. However, it does not explicitly state when not to use or cite alternatives like get_hourly_forecast for hourly needs.

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