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

Beyond the annotations (idempotent, non-destructive, open-world), the description adds real behavioral context: it requires a wallet-session Bearer token, clarifies that no funds move at creation time, and warns there is no escrow protection for direct payments. Those are exactly the caveats an agent needs before invoking a payment tool.

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?

Four short sentences, purpose front-loaded, followed by auth requirement, idempotency rule, and safety caveats. No filler, though the final two sentences ('No funds move' / 'no escrow protection') could be merged.

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 5-parameter payment-creation tool with no output schema and 0% schema coverage, the description covers auth and safety well but omits any parameter explanation. An agent can understand the operation's nature but not how to correctly populate most of the arguments.

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 0% for 5 parameters, so the description carries the full burden — but it only touches operation_id (retry semantics). chain_id, amount_atomic (atomic units?), asset (default USDC), and memo are left completely undefined in both schema and description.

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 states a specific verb and resource ('Create a ... token request') and narrows it with meaningful qualifiers: zero-service-fee, allowlisted, and payable to the authenticated wallet. It does not name a distinguishing sibling from the crowded payment-request family (create_solana_payment_request, prepare_payment), so an agent still has to infer the scope split.

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 one concrete operating rule — 'reuse operation_id only for identical retries' — which is genuinely actionable. However, it never says when to choose this over siblings like create_solana_payment_request or prepare_payment, so the routing guidance is only implied.

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