nws_zone_forecast

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

The annotations already declare readOnlyHint=true, and the description is consistent with a read operation. However, the description adds no additional behavioral context beyond that, such as return format or rate limits, but for this simple tool the annotation covers the key trait.

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 only two sentences, with the purpose front-loaded and a helpful second sentence providing a concrete example of a zone ID. There is no unnecessary verbosity or wasted content.

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 one-parameter read-only tool, the description adequately covers the purpose and parameter format. It could mention alternatives or output details, but these are not critical for such a straightforward tool. The coverage is nearly 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?

The input schema has 100% coverage, describing zone_id with the same example format ('NYZ072', 'CAZ006'). The tool description repeats this example, adding no extra semantic value beyond what the schema already provides.

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 'Get text forecast for a specific NWS forecast zone', which is a specific verb+resource+scope. It distinguishes from sibling forecast tools like nws_forecast_hourly and nws_alerts_active by focusing on text forecasts for a specific zone.

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 implies usage when a specific NWS zone ID is known, but it does not explicitly explain when to use this tool versus alternatives such as nws_point_lookup or nws_forecast. No exclusionary guidance is provided.

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