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

Annotations already cover safety (readOnly, idempotent, openWorld, non-destructive), so the description's value-add is the caching window ('cached for 10 minutes') and the graceful-degradation note that it still works without INAM data. It also discloses what third-party signals are consulted (402 requirements, ERC-8004, Web Bot Auth, domain age), which the annotations cannot convey.

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 purpose is front-loaded in the opening clause, followed by data sources and then return shape. It is dense but the clauses are informative rather than redundant; the return-field enumeration could be trimmed slightly given the readOnly/idempotent profile.

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 present, the description carries the return-value burden and discharges it fully (verdict, checks[] with status/label/detail, payment, next, cachedAt). It also covers the fallback path and caching, leaving no obvious gap for a 2-parameter read tool.

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%, so both parameters are already documented, and the description duplicates the target-type list without adding syntax or format detail. The 'method' parameter and its POST caveat are never echoed in the description, so no value is added beyond the schema.

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 (check) and enumerates the accepted target resources (x402 URL, EVM wallet, did:key) plus the operative context 'before paying it'. An agent can tell this apart from inam_check_reputation or inam_verify_receipt because it is framed as a consolidated pre-payment gate, not a single-signal lookup.

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?

'before paying it' gives a clear trigger condition, and 'Works when INAM has no data on the target' sets expectations for a weak-signal case. However, it never names a sibling as the alternative (e.g., when to prefer inam_check_reputation directly), so there are no explicit exclusions.

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