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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful context beyond annotations: the data source (Tips contract PurchaseCompleted logs on the Hedera mainnet mirror node), ordering (newest first), and cross-device source-of-truth alignment with the dapp page.

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 sentences, front-loaded with the core purpose and return fields. The provenance sentence is longer but earns its place by establishing data trust and source; no obvious filler.

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 one-parameter, read-only tool with no output schema, the description covers what is returned (listing titles and transaction ids) and ordering. It does not address pagination or result limits for a potentially large 'list every' response, leaving a minor gap.

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 description coverage is 100%, and the description repeats the accepted wallet formats (0.0.x account id or 0x EVM address) without adding new syntax, constraints, or validation details. The schema already carries full parameter documentation, so this is 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?

States a specific verb (list) and resource (verified on-chain marketplace purchases for a wallet), including ordering and returned fields. It does not explicitly differentiate itself from siblings such as verify_purchase or recent_tips, so 4 rather than 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?

Implies usage: fetch a wallet's purchase history by passing an account id or EVM address. However, it gives no explicit when-to-use guidance, no exclusions, and does not name alternatives such as verify_purchase for single-purchase checks.

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