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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered, but the description adds substantial context they cannot: a concrete price per call, the two payment rails (xrpl:0 and eip155:8453), the exact failure shape (isError with an x402 PaymentRequired object carrying a fresh invoiceId), and that unpaid calls cost nothing. That is real behavioral disclosure beyond structured fields. It does not say whether the underlying data is cached, throttled, or how stale asOf can be, which keeps it from 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 core question and the payment mechanics are front-loaded and every clause carries information; the title repeats the pricing, causing some redundancy. It is a dense block rather than a structured list, but nothing is padding.

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?

With no output schema, the description usefully names the returned fields (per-provider indicators, reason, asOf, observed_uptime_7d, attribution) and fully specifies the payment handshake and error path. What is missing is which providers are covered and how this differs from the adjacent decision/status tools, which matters given a crowded sibling set.

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 100% and the single parameter is already documented, so the baseline is 3. The description still earns credit by explaining the alternative transport (_meta["x402/payment"]) and the sequencing rule that the parameter should be omitted on the first call — meaning the schema alone would not tell an agent when to supply it.

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 concrete verb+resource: it returns "raw per-provider indicators, reason, asOf, and observed_uptime_7d samples" from public AI-provider status pages, framed as answering one question. That is far more specific than the name alone. It stops short of distinguishing itself from close siblings such as decide_provider_health, get_service_status, or get_pulse_storm, so an agent still has to guess which of those to pick.

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 guidance is strong on the payment path — omit payment on the first call, receive the PaymentRequired object with a fresh invoiceId, then retry with the signed payload — but there is no guidance on when to use this tool versus the sibling health/decision tools in the same family. The when-to-pay flow is explicit; the when-to-call context is only implied by the framing question.

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