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

With annotations only covering readOnly/idempotent/destructive/openWorld, the description adds substantial behavioral context the annotations do not: bearer-key auth requirement, zero data-credit consumption, reads Solana at finalized with specific validation fields, and the explicit assurance it never broadcasts. It also maps 400/404/409/503 to concrete meanings.

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 purpose is front-loaded and no sentence is filler — error codes, idempotency, and next-step routing all carry operational value. Slightly dense as a single run-on block with irregular indentation, but every clause earns its place.

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 confirmation call with an output schema, the description still supplies everything an agent needs: auth, side effects (activates package, no credits), idempotency behavior, the full error taxonomy, and the follow-up tool sequence. Nothing material is missing.

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%, so the schema already documents signature (base58, not a login signature/private key) and invoice_id (from get_payment_instructions, not a swap id). The description adds no parameter-level syntax or format detail, so the baseline 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?

States a specific verb+resource ('Verify an already-broadcast invoice payment and activate the purchased data package') and explicitly scopes it to payments already broadcast, which cleanly separates it from prepare_invoice_payment and get_invoice_status. An agent can pick this without opening a sibling schema.

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?

Gives explicit preconditions (payment must already be broadcast, bearer key for the invoice owner), post-success routing ('use get_access_status, then get_recent_trades or get_stream_connection'), and retry guidance tied to a specific status ('409 ... retry this confirmation with backoff, not the payment'). Alternatives and exclusions are named rather than implied.

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