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

Adds value beyond annotations by disclosing the auth requirement (API key), the intended follow-up action, and the memo format. The readOnlyHint is consistent with a tool that only builds an unsigned transaction without submitting it, so there is no contradiction. It doesn't mention expiry, replay, or error behavior, keeping it at 4.

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 tightly packed sentences, front-loaded with the return value and flow, with zero filler. Every clause carries information the agent needs.

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?

Although there is no output schema, the description fully describes the return (unsigned base64 transaction), the required follow-up steps, and the auth prerequisite. Nothing needed to call it correctly 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 coverage is 50% (buyer_wallet documented, order_id not), and the description compensates by tying order_id to the order price and the memo dollarr:<orderId>, and clarifying that buyer_wallet signs and pays the fee. This adds genuine meaning over the raw 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?

States a precise verb+resource (builds an unsigned Solana USDC-to-escrow transaction), names the exact return format (base64), and distinguishes itself from the sibling confirm_payment by describing the two-step flow. An agent can tell this apart from confirm_payment without opening either 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 clear sequencing: sign with buyer_wallet, send it, then call confirm_payment. It tells the agent where this sits in the workflow. It stops short of explicit when-not-to-use guidance (e.g., don't call once payment is confirmed), so it doesn't reach 5.

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