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

Well beyond the annotations, the description discloses the data source (the published Atlas dataset read once per call), that there are no dataset writes and no issuer contact, the version stamping behavior, the current_version_only return case, and the not-in-published-dataset fallback. It also discloses the commercial terms (0.10 USDC on Base via x402 exact, 10 free signed-wallet calls per 30 days) and the X-Wever-Wallet-Proof binding requirement to the exact JSON arguments and route.

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?

It is front-loaded with the purpose, which is good, but the remainder is a dense run-on packing version semantics, payment terms, wallet-proof binding, a contract path, and a human URL into one paragraph. Each item has some value, yet the structure makes it easy to miss the payment and header-binding requirements.

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?

For a paid, signed-receipt tool with no output schema, the description covers the essentials: input form, data source, version semantics, fallback states, and authentication/payment mechanics. It stops short of specifying the report's field layout beyond the receipt and version stamp, but an agent has enough to call it correctly.

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% and the single asset parameter already documents case-insensitive matching, the pattern, and the paxg/PAXG example. The description restates that an id or ticker is accepted and adds nothing about resolution precedence between an id and a ticker, so it sits at the baseline.

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 names a concrete verb and resource: it takes an asset id or ticker and returns the signed report of how each of six rights fields moved across published dataset versions. That distinguishes it from generic lookup siblings, but it never contrasts itself with close siblings such as wever_atlas-rights-gap or wever_atlas-asset-passport, so differentiation must be inferred from the field-history framing 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?

There is no explicit when-to-use or when-not-to-use guidance, and no named alternative among the many atlas-prefixed siblings. The agent can infer the use case from the purpose statement, but must guess whether a gap check or a passport lookup would be the better first call.

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