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

Goes well beyond the annotations: discloses a $0.005 x402 payment in USDC on Base, that the settlement receipt becomes the claim's proof, the 24h rate limit, and the decay timeline (ALIVE → LIKELY ALIVE → UNTESTED after 14 days). None of that is derivable from readOnlyHint/idempotentHint alone.

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?

Purpose is front-loaded in the first clause and every sentence carries substantive information (cost, proof, cadence, decay, override, inputs). It is dense but not padded; a slight restructuring into shorter sentences would improve scannability.

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 an output schema present and annotations covering safety and idempotency, the description fills the remaining gaps an agent needs: payment mechanics, rate limit, status lifecycle and precedence rules.

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 baseline is 3; the description still adds value by saying 'exact service name (from search_services, free)' and reinforcing that status must be LIVE, which clarifies provenance and the constraint's intent.

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 ('self-report your endpoint as LIVE') plus the audience ('for service providers'), which cleanly separates it from siblings like search_services, request_review or accept_retest_quote.

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 context: providers report their own service, one report per 24h, and UseTested's own sweep results override self-reports so the agent knows when this is not authoritative. It also points to search_services for obtaining the exact name. It stops short of explicitly naming competing siblings as alternatives.

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