nws_forecast

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

The readOnlyHint annotation is consistent with the 'Get' verb. The description adds useful behavioral context by specifying the return content: 'Returns forecast periods with temperature, wind, and conditions.' It also clarifies that lat/lon auto-resolves the grid, complementing the schema description.

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 three concise sentences, front-loaded with the main purpose. Each sentence adds value: what it does, how to invoke it, and what it returns. No filler or redundancy.

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?

With 5 parameters and no output schema, the description compensates by covering both input modes and describing the return structure. It could mention units or timezone, but for a read-only weather forecast with clear annotations, this is adequately complete.

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%, providing descriptions for each parameter. The description adds crucial semantic meaning by stating the EITHER/OR relationship between the two input groups, which is not evident from individual schema descriptions and helps avoid invalid combinations.

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 opens with a specific verb and resource: 'Get 7-day weather forecast.' This clearly states what the tool does and the 7-day scope distinguishes it from sibling nws_forecast_hourly. No ambiguity.

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 explicitly explains two mutually exclusive input modes: office+grid coordinates (from a point lookup) OR latitude/longitude to auto-resolve. This gives clear when-to-use guidance for parameter selection. However, it does not explicitly mention alternatives like nws_forecast_hourly when hourly data is needed.

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