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

Annotations already indicate read-only and idempotent behavior. Description adds value by specifying the data source (U.S. NWS) and output format (7-day day/night or hourly up to 48 periods). No contradictions.

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?

Two sentences efficiently convey core purpose, source, location, output options, and parameter effect. No superfluous information.

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?

Given the tool's simplicity (one optional parameter, clear output schema), the description fully covers what the agent needs: source, location, output options, and parameter usage. Annotations handle behavioral transparency.

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 single parameter `hours` is already well-described in the schema (limit 1-48). The description reinforces its purpose and adds context ('through about two days out'), providing marginal additional clarity beyond schema.

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 returns a forecast from the U.S. National Weather Service for Crosby, TX. Differentiates from sibling tools like get_current_conditions by specifying it's a forecast, either daily or hourly.

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?

Explains when to use daily vs hourly forecast via the `hours` parameter. While it doesn't explicitly exclude alternatives, the context is clear enough that the tool is for forecasts, not current conditions or other weather data.

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