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

With no annotations provided, the description carries the full burden and does so reasonably well: it discloses the operation is offline and free, that results are per-receipt valid/invalid, and what the response contains (signer recovery, declared signer comparison, integrity digest). It does not cover failure modes such as malformed receipt JSON, which keeps it from a 5.

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?

Three tight sentences: the core action and cost signal come first, the return shape second, and the batch input format last. Nothing is repeated and every sentence carries information an agent needs.

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?

There is no output schema, so the description correctly compensates by summarizing the per-receipt return fields. Combined with the documented parameters, an agent has enough to call it correctly; only error/failure behavior is left unstated.

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 the baseline would be 3. The description adds genuine value beyond the schema by clarifying that raw_receipt accepts a single JSON string or an array for batch verification, which conveys the batch semantics at a glance. It says nothing about settlement_asset, which explains why it is not a 5.

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 specific verb and resource: 'Verify one or more XDR-1 signed receipts offline', and adds the key scope of batch support. It does not explicitly contrast with the sibling bundle_verify, which is the one tool an agent might reasonably confuse it with, so it stops short of a 5.

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?

Mentioning 'offline (free)' implicitly signals no network call and no cost, which is useful context for choosing this over on-chain checks. However, it never states when not to use it or names an alternative such as bundle_verify, so the guidance remains implied rather than explicit.

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