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

Goes well beyond the readOnlyHint/openWorldHint annotations: it discloses exact pricing (0.001 RLUSD on XRPL or 0.001 USDC on Base), the failed-call behavior (isError with a fresh x402 PaymentRequired invoiceId), the retry paths (_meta["x402/payment"] or payment_signature), the meaning of each reading value, and the unrouted providers whose status is null until 2026-11-12. This is rich, decision-relevant disclosure that an agent could not derive from the schema.

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?

Front-loads the payment cost first, then usage, return values, deprecation status, and failure handling. Every sentence carries information, though the payment bootstrapping details and the return-value enumeration make it dense relative to a two-parameter tool.

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?

There is no output schema, so the description must explain returns — and it does, enumerating go/caution/no_go/unknown, the derived handling flag, and the 24h disturbed-check share. Combined with the payment failure/retry flow and the null-status provider list, an agent has everything needed to call and interpret this correctly.

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%, so the schema already documents both parameters well, including the vendor-slug/model-id formats and the payment_signature role. The description adds little parameter-level detail beyond echoing the payment_signature/x402 mechanics, so it sits at the documented baseline.

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 'pre-flight conditions reading' of AI provider health from vendor status pages. It is clear what the tool does, but it never names or contrasts the near-siblings get_service_status, get_current_conditions, or get_pulse_providers, so an agent must infer the split itself.

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?

'Use when an agent is about to call an AI provider and wants a pre-flight conditions reading' gives a concrete triggering context. However, it offers no when-not guidance and no named alternative for cases where a different status tool would be the right pick.

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