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

With no annotations, the description carries the full burden and does disclose meaningful traits: a 31-day horizon cap, a labeled method, station-vs-point coverage limits with the INVALID_PARAMS failure mode, NWS-derived sourcing, market cross-referencing, and a $0.05 x402 price. It omits return-value shape and any auth/rate-limit detail, keeping it below a 5.

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 key scope statement is front-loaded and the sentences are dense but purposeful, covering deliverable, coverage limits, and cross-referencing. The trailing HTTP/price/docs block is useful metadata rather than filler, though the whole is packed tightly enough to be a little heavy.

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 an 8-parameter, annotation-free tool with no output schema, the description covers coverage/behavior/pricing well but should explain the response shape (probability value, method label) since no output schema exists. Half the parameters and the return format are left to inference.

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 only 38%, so the description must compensate, and it partially does by tying condition values (temp_above/below, precip, wind, named storm) to coverage behavior and clarifying window_stat max/min semantics. It adds nothing about lat/lon, city, threshold units, or the window date bounds beyond what the schema already states.

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 states a specific deliverable – the model's probability that a weather condition occurs in a future window – and scopes it (temp at covered stations, precip/wind at any US point). It implicitly distinguishes itself from the market-based siblings like edge_weather-markets by noting it cross-references, rather than returns, market data. It stops short of naming an alternative tool explicitly.

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?

It gives real usage constraints (temp events only work at model-covered stations and otherwise return INVALID_PARAMS; precip/wind/named-storm work for any US point), which tells the agent when a call will succeed. However, it never routes the agent to a specific alternative when the condition is unsupported, so the 'vs alternatives' guidance remains implied.

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