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

With no annotations, the description carries the full burden and does so well: it discloses the minute-resolution counter basis (~720 samples/provider/day), which fields require payment, the x402 transport URL, Bearer token alternative, and the free-trial credit path. It is thin only on return shape beyond the two paid fields.

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 ranking and window semantics are front-loaded, and pricing/auth details follow in the right order. It is dense and packs two long URLs, but each sentence carries operational information an agent needs to call it correctly.

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 a paid read tool with no output schema and no annotations, the description covers computation, cost, and auth completely. The remaining gap is the default (unpaid) response fields, which an agent can only partially infer from the incident_count/mttr_minutes mention.

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%, so the schema already documents days, tier, and payment. The description largely restates the same tier/pricing semantics and adds only the note that payment can arrive via arguments.payment or an X-PAYMENT header — useful but marginal, so the baseline 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?

States a specific verb+resource: a cross-provider uptime leaderboard ranked by uptime % DESC, which is meaningfully distinct from single-provider siblings like status_uptime or get_status_summary. It falls short of a 5 only because it never names the adjacent tools it should be chosen over.

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?

Gives clear conditions for the paid path: days 1-7 free, 8-90 costs 5 credits, and tier='full' forces paid fields at any window. It explains payment/token prerequisites but offers no explicit when-not or sibling routing (e.g., when to use status_uptime instead).

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