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

Goes well beyond the readOnlyHint/openWorldHint annotations: discloses the $0.01 USDC-on-Base x402 price, that payment settles before execution, that a free probe call rejects calls that would fail, and that results verify offline against a public key from /menu. These are exactly the operational facts an agent needs before spending money.

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?

Price and payment protocol are front-loaded, which is good, but 'Full signed history and current values, verifiable offline' is immediately repeated in the next sentence, and there is a stray double period ('..'). Roughly a quarter of the text is redundant.

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 does describe the payload (signed history plus current values, offline-verifiable against /menu's public key) and covers the payment handshake. Adequate for a one-parameter paid export, though it could say whether the export is paginated or bounded for large histories.

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?

The single parameter is already fully documented in the schema ('Only entries after this seq'), and the description's 'returns only newer entries' restates it with slightly different wording rather than adding semantics. With 100% schema coverage, 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?

States a specific verb (export) and a precise resource (the paying wallet's persistent key-value store: full signed history plus current values), with the added qualifier that the output is offline-verifiable. It implicitly distinguishes itself from read-only siblings like tabularium_read by emphasizing backup/proof of the complete signed chain, but it never names an alternative explicitly.

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 use cases ('for backup or proof') and a concrete invocation protocol: call once unpaid to learn the price, then retry with params._meta["x402/payment"]. What's missing is explicit routing versus siblings such as tabularium_read or tabularium_snapshot_fetch for partial reads.

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