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

Goes well past the annotations: discloses the paid x402 exact model at 0.10 USDC per call on Base, the 10 free signed-wallet calls per rolling 30 days, the X-Wever-Wallet-Proof binding to exact JSON arguments and route, the Ed25519 signed receipt on the return, and the scope limits (no page fetch, no account access, no money movement). It also states the analytical boundary — the report matches words, figures, dates and named items but does not interpret meaning.

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 purpose is front-loaded and nearly every clause carries information, but it is delivered as one dense run-on paragraph with nested parentheticals that make it hard to scan. The trailing contract path and human page URL are useful but tacked on without structure.

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 steps in to describe the return: missed-commitment verdict, point shortfall, credit band, percentage, cap, amount, request deadline, all quoted, plus a signed receipt. Payment/auth mechanics and the matching-only limitation are covered, so a caller has everything needed to invoke and interpret it.

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 already 100%, so the baseline is 3, but the description adds real meaning: it explains the two input modes (raw text vs structured month/outages/downtime/stated uptime), why stated uptime is compared against computed uptime, and that scheduled maintenance or degraded time is set apart when the terms exclude it. The optional fee and currency role in producing a credit amount is also made explicit.

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 concrete verb and resource: submit SLA terms plus an outage/service report, compute uptime exactly from period minutes and counted downtime, decide whether the commitment was missed, and name the prescribed credit band with percentage, cap, amount and deadline. The framing ('DiligenceOps') plus the POST route makes it distinguishable from evidence-check siblings like wever_sla-evidence-check or wever_agent-sla-rail.

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 implies the usage context (you have SLA terms and an outage/service report and want a credit determination) and rules out implicit data gathering ('reads only the material in the call'), but it never names an alternative tool or states when a caller should pick wever_sla-evidence-check or wever_agent-sla-rail instead. The x402 pricing/free-call terms add cost context but not use-vs-alternative guidance.

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