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

Annotations already establish read-only, non-destructive, closed-world behavior, and the description adds auth requirements ('Requires auth and read:bids scope') plus the live nature of the data ('one row from the live offer book'). It does not describe error behavior for a stale or missing identifier, which keeps it from a 5.

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?

Content is front-loaded with the resale order book context, then the usage condition, then alternatives. Slightly verbose with multiple parenthetical tool names, but each clause carries routing or scope information.

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 an output schema, full parameter schema coverage, and clear annotations, the description fills the remaining gaps: when to use it, which siblings to prefer instead, auth/scope requirements, and that it returns a single row of live offer data. Nothing an agent needs in order 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 100% and the parameter's description already says the identifier is a public listing ID from list_open_listings. The prose adds only that the identifier must already be in hand; it does not expand on format or provenance beyond the 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 specific verb and resource: fetch the full record for one open listing by identifier. It explicitly distinguishes itself from list_open_listings (the list variant) and from search_events/get_ticket_listings (the plain buy-now path), so an agent can tell exactly which tool this is.

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 a precise trigger ('when a listing identifier is in hand' and before make_offer_on_listing or buy_listing_now) and a precise exclusion ('for a plain buy-now at the asking price without an offer, use search_events and get_ticket_listings instead'). Alternative tools are named explicitly.

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