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

With no annotations provided, the description carries the full burden and adds valuable behavioral context: it explicitly states 'No mock radar', meaning results are real, and defines failure semantics ('a failed fetch is CURE'). It also mentions output components like altitude tops and movement vectors. The meaning of 'CURE' is not expanded, but the core trust and failure behavior is disclosed.

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 two dense sentences with no fluff. The main purpose is front-loaded, lane-specific outputs are separated clearly, and the behaviora note about mock data and failures earns its place. Every sentence contributes.

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 explains the primary lane parameter and gives a good sense of the returned data, but there is no output schema, so return format is not specified. Two of three parameters are left undocumented, and no guidance is given for what happens if lane is omitted despite being non-required in the schema. The core use case is clear, but completeness has clear gaps.

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 only 33%, so the description must compensate for the undocumented parameters. It does explain lane in detail, mapping each value to its output. However, wallet_hash and c4_invariant_scf are completely unexplained both in schema and description. An agent cannot infer their purpose or whether they are needed, which is a significant gap.

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 what the tool does: it returns live NOAA weather data for an aviation radar lane, with distinct outputs for lane=weather (convective SIGMET polygons) and lane=space (GOES-R X-ray flux and aurora). The level of specificity distinguishes it from general weather tools and from the sibling weather.convective_containment, even without naming alternatives.

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 gives clear context for choosing between the two lane values, explaining exactly what each returns. It does not explicitly mention alternatives or exclusionary conditions relative to sibling tools, but the internal lane routing is well specified. This is more than implied usage, though not a full when-to-use vs alternatives guide.

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