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

Annotations only cover the safety profile (readOnlyHint false, openWorld true, idempotent false, destructive false), while the description adds real behavioral detail: one live GET (with indexed-URL method exception), public hosts only, redirects re-checked, delisted hosts never contacted, 60 s caching, and concrete rate limits (3/host/5 min, 30/min). That is exactly the kind of context annotations cannot carry.

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 use case and the caveat, then packs the network and rate-limit constraints into a dense second sentence with no filler. The semicolon-chained clauses are information-always but make the sentence heavier than necessary.

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?

An output schema exists, so return values need no prose explanation, and the description still summarizes what is reported. Between the description and schema an agent knows the request semantics, side-effect profile, host restrictions, caching and throttling before calling – nothing material is missing.

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 both parameters are already documented. The description's method rule and 'public hosts only' constraint simply restate what the url and method schema descriptions say, adding no new syntax or format guidance beyond the structured fields.

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 and resource ('probe one URL for a well-formed x402 challenge') and scopes it to a live unpaid request that reports status code, latency, alive flag, challenge presence and parsed USD price. This is clearly distinguishable from siblings like x402_search or x402_index_stats, which do not issue live probes.

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 explicit context for use ('a URL you are about to pay (or one you operate)') and a valuable caveat that a challenge is no guarantee the service delivers, which frames the decision to send funds. It never names an alternative sibling or an explicit when-not-to-use, so it stops short of the top bar.

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