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

Goes well beyond the annotations by disclosing concrete cost ($0.005 per call), the payment rail (USDC on Solana via x402), the two-step MCP challenge/retry flow, and an HTTP fallback endpoint. This is consistent with readOnlyHint=false and idempotentHint=false. It stops short of saying what happens on payment failure or whether a failed estimate still charges.

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, purpose front-loaded, operational details second. The payment sentence is dense but every clause carries information an agent needs to actually complete a call.

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?

With no output schema, the description should hint at what comes back — a fee breakdown by signature/priority component, units, or confidence — and it says nothing. The billing and transport story is complete; the result story is absent for a tool whose whole point is producing an estimate.

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 three parameters are already documented in structured form, and the description adds nothing about accounts, priority levels, or the transaction_base64-vs-accounts choice. 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 and resource: 'Estimate a Solana transaction's total fee cost.' That cleanly separates it from chain-agnostic or optimization siblings, though it never names fees_optimize or tron_estimate as the alternatives an agent should weigh.

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 invocation protocol is spelled out well (call without payment, read the PaymentRequired challenge, retry with _meta["x402/payment"]), which is genuinely useful. But there is no guidance on when this tool is the right choice versus fees_optimize or tron_estimate — selection between siblings is left to inference.

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