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

Annotations only cover the shallow profile (openWorldHint, non-idempotent, non-destructive), while the description adds real behavioral context: the invoice is paid externally and the balance updates only after confirmation, crypto carries no fee but card adds 2.9%, balance never expires and is non-redeemable, minimum $1, and a connected agent wallet is required. This is materially more than the annotations provide.

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?

It is well front-loaded (purpose, then return value, then usage, then caveats and prerequisites) and every section carries information. However, the supported-asset list is effectively repeated twice (once as accepted coins, once as returned native destinations), which costs a sentence of redundancy in an otherwise tight block.

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 must describe the return value itself, and it does: a payment page link, per-coin crypto payment details, and the confirmation-driven balance update. Combined with the deposit minimum, fee model, and auth requirement, an agent has everything needed to call it and interpret the result.

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 is 3, but the description adds real meaning: it explains the intent behind the `coin` enum (only pass USDT-TRON if you will actually pay in USDT, since those addresses come from a small pool) and clarifies that `amount` is the credited USD figure rather than the total charged. Only the credit-vs-fee arithmetic for card payments could be stated more precisely.

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 first sentence states a specific verb and resource ('Creates a payment invoice to add funds to the connected prepaid PikaSim Wallet') and immediately names the artifact returned (payment page link plus per-coin crypto details). It is clearly distinguishable from siblings like purchase_esim or topup_esim because it funds prepaid credit rather than buying a product.

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?

It gives an explicit trigger ('Use when check_balance is too low to purchase'), names the sibling that supplies that condition, and clarifies the boundary that this tool does not itself move funds or purchase anything. That is enough for an agent to route correctly without opening other schemas.

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