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

With only readOnlyHint/openWorldHint/idempotentHint from annotations, the description carries substantial extra weight and delivers: exact cost per call on two chains, the 60-second cache window, the unpaid-call behavior (isError with a fresh x402 PaymentRequired invoiceId), and the exact retry path via _meta["x402/payment"] or payment_signature. This is exactly the payment/error semantics an agent needs and that annotations cannot express.

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 dense but every block (price, purpose, return shape, sources, cache, payment flow) is load-bearing. Slight redundancy in restating payment twice (price line and retry instructions) and the purpose statement sits after the pricing preamble, costing a little front-loading.

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?

No output schema exists, and the description compensates by enumerating the return fields (storm, level enum, one reason, asOf, sources) and the source metadata (attribution, terms_url, not_affiliated). Combined with the full payment and caching story, an agent has everything needed to invoke and interpret this tool.

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 100% for the single payment_signature parameter, and the schema already documents its Base64 PAYMENT-SIGNATURE meaning and the 'omit on first call' behavior. The description largely restates that in the payment-flow sentence, so the baseline of 3 applies.

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 verb and resource — a combined 'storm signal' reading that aggregates the worst current level across tracked public status pages plus measured facilitator reachability and recent changes. It clearly distinguishes itself as an aggregate/composite read from the narrower siblings (get_pulse_facilitator, get_pulse_providers), though it never names those siblings 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?

Usage is only implied: 'small loop-friendly' and 'cached up to 60 s' tell an agent this is a cheap polling/aggregate check, but there is no explicit when-to-use versus get_pulse_providers or get_current_conditions, and no stated exclusions. The agent must infer routing from the composite nature of the reading.

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