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

Beyond the readOnly/openWorld annotations it discloses concrete operational traits: one dataset read per call, no writes, no issuer contact, dataset version stamped on every report, absent fields reported as 'not in the published dataset', x402 pricing at 0.10 USDC on Base, a 10-call free tier per rolling 30 days, wallet-proof binding to the exact JSON arguments, and an Ed25519 signed receipt.

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 in the first sentence and the long enumeration of report contents earns much of its length because no output schema exists. Still, the paragraph is a dense run-on mixing return values, billing, auth, and contract URLs, which could be split or trimmed.

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 must carry the return surface and it does so thoroughly, covering report sections, versioning, and null-result semantics, plus payment and auth mechanics. It omits failure behavior (invalid asset, exhausted free tier, payment rejection), which is the main remaining gap for an agent to call it confidently.

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?

There is only one parameter and schema coverage is 100%, with the schema itself supplying the case-insensitive match rule and a worked example. The description's 'asset id or ticker' restates the schema's meaning without adding syntax, formatting, or disambiguation guidance, so the baseline 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?

The description states a specific verb and resource combination ('Atlas evidence' on a redemption right for a given asset id or ticker) and enumerates what the signed report contains. It is clearly distinguishable from general asset lookups, but it never names the closest siblings (atlas-rights-gap, atlas-rights-history, atlas-nav-evidence), so an agent must infer the boundary from the word 'redemption' alone.

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?

Usage is implied rather than stated: 'submit an asset id or ticker' and the enumeration of redemption-specific questions suggest when the tool is appropriate. There is no explicit when-not guidance and no named alternative for neighbouring evidence questions, leaving sibling selection to inference.

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