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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real value beyond them: 0.10 USDC per call on Base mainnet via x402 exact, 10 free signed-wallet calls per rolling 30 days, and X-Wever-Wallet-Proof binding the exact JSON args to the path. Some content (escrow 300 USDC cap, Duffel test mode, booking vs quote approval) describes surrounding domain rules rather than this read call, costing it a point.

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?

Purpose is correctly front-loaded, but the body is a run-on sequence of loosely related statements, several of which belong to the booking/escrow tools rather than a status read. A reader must parse the whole block to find the operative facts (price, auth header, reconciliation use).

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 single-parameter read with no output schema, it does cover what is returned, the payment model, the auth mechanism, and points to /api/sports-trips-contract for schemas and receipt verification. Remaining gap is the trip_id contract and error/reconciliation behavior on failure.

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% and the only parameter, trip_id, is never explained in the description – not its st_ + 64 hex format, not where it comes from (presumably sports-plan-trip). 'Your trip' is the only hint, so the description fails to compensate for the schema gap.

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?

Opens with a specific verb and resource ('Read the itinerary, current leg states, exact prices, approval records and signed receipts for your trip'), so the agent knows exactly what data comes back. It never names the sibling sports tools (sports-plan-trip, sports-book-leg, sports-cancel-leg) to draw the boundary explicitly, which keeps it from a 5.

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?

'Uncertain attempts are reconciled through trip-status' gives one concrete use case, and 'Read /api/sports-trips-contract for schemas...' routes the agent to a companion resource. However, there is no statement of when to prefer this over sibling trip/leg tools, and no explicit exclusions.

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