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

Annotations declare a non-read-only, open-world, idempotent, non-destructive tool; the description adds substantial value beyond that. It discloses the 400-rejection of private IPs, that each call appends a timestamped observation, that rug_pulls increments on tools_hash drift, that it writes to a public ledger, the first-5-calls/IP free tier, and conditional idempotency on steady schemas. This richness is well above the annotation baseline.

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?

Dense but front-loaded: purpose first, then constraints, effects, and routing alternatives in a compact block with a concrete example. Each sentence carries weight, though the single long opening paragraph packs several concerns together and could be marginally more scannable.

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-value explanation is unnecessary, and annotations already carry the safety profile. The description covers the remaining agent-critical facts: eligibility constraints, side effects on the public ledger, drift counter behavior, rate limits, and idempotency semantics.

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% for the single 'target' parameter, and the schema already states that private/loopback IPs are blocked. The description restates the public-HTTPS constraint and format but adds no syntax, normalization, or validation detail the schema lacks, so the baseline of 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 (register/refresh a remote MCP, A2A, or x402 endpoint dossier) and names the mechanism (live HTTP, agent-card, JSON-RPC tools/list inspection without policy gating). The agent can distinguish this onboarding/re-indexing action from the sibling gating, ledger, and verification tools without opening any schema.

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?

Explicitly routes the agent: 'Use to onboard or re-index a server' plus three named alternatives with selecting conditions (pre-call gating -> assay_preflight, historical observations/hash pinning -> assay_get_ledger_policy, post-payment disputes -> assay_verify_delivery). Nothing is left to inference.

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