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

No annotations provided, so the description carries full burden. It discloses that rewardCommitmentToken and batchAnchor may be null due to asynchronous batching, and instructs on checking per-step verification results. This goes beyond basic function to explain behavioral nuances.

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 description is concise with upfront purpose and subsequent detail. Each sentence adds value, though it could be slightly more streamlined without losing information.

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?

Given the tool has one optional parameter, no output schema, and no annotations, the description provides comprehensive context: what the bundles contain, their limitations, handling of null fields, and verification instructions. This is sufficient for an agent to understand invocation and interpretation.

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% with a clear description for the single 'limit' parameter. The description does not add further semantic value beyond what the schema already provides, so baseline score of 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 clearly states the tool retrieves 'recent gateway-issued artifact bundles for portable spend/GMV verification' and lists specific items included. It distinguishes from sibling tools like 'get-gmv-inclusion-proof' by focusing on recent bundles.

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?

The description provides context on what the bundles are used for and explicitly clarifies they are not proof of Bitcoin settlement or chain finality. It directs users to check 'steps' and 'ok' fields. However, it does not explicitly state when to prefer this tool over siblings or exclude scenarios.

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