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

With minimal annotations (readOnlyHint false), the description adds value by stating the outcome: returns a payment address and amount, and that the wallet is credited on blockchain confirmation via webhook. It could mention network fees or confirmation times, but the provided transparency is above average.

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?

Two sentences deliver the essential information without wasted words. The structure is clear: action, accepted coins, return values, and confirmation mechanism.

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's moderate complexity and the presence of an output schema, the description covers the basic flow. However, it fails to differentiate from sibling wallet.deposit and does not address the schema contradiction, leaving context gaps.

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%, but the description contradicts the schema by stating only USDC and USDT are accepted, while the enum includes BTC and ETH. This misalignment undermines parameter understanding. No additional semantic detail is provided beyond what is in the schema.

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 creates a cryptocurrency payment to top up a wallet, with a specific verb ('create') and resource ('cryptocurrency payment'). It distinguishes from siblings by specifying the payment method (crypto vs fiat), but the discrepancy between the description (USDC and USDT only) and the input schema enum (includes BTC and ETH) reduces clarity.

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 no guidance on when to use this tool versus alternatives like wallet.deposit, which likely handles fiat deposits. No exclusions, prerequisites, or context for choosing crypto over other deposit methods are given.

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