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

Annotations already declare read-only, non-destructive, non-open-world, but the description adds substantial behavioral context the annotations cannot supply: the requires-auth and read:bids scope, the special sold/awaiting-transfer result shape with transfer instructions and remaining obligation, and the USDC 6-decimal raw-unit encoding for amount_raw plus human-readable amount_display.

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?

The primary purpose arrives second; the description opens with a narrow edge case (sold listing awaiting ticket transfer) that is not the main use case. The body is information-dense and useful but meanders between units, scopes, and routing before the core function is established.

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?

An output schema exists, so return values need not be restated, and the description still adds the one thing the schema can't convey (USDC raw-unit encoding and the sold-listing transfer case). Auth, scope, seller-side positioning, and alternatives are all covered for a one-parameter read tool.

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% for the single identifier parameter, and it even points to list_open_listings/list_my_listings as its source. The description adds nothing extra about the parameter but does clarify the semantic result fields (actions mapping to accept_offer/reject_offer), slightly exceeding the baseline given full schema coverage.

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 — polling an authenticated seller's own listing to see open bids, state, and seats — and explicitly names it as 'the seller view of the live offer book.' An agent can distinguish it from sibling read tools like get_open_listing, check_listing, and search_market.

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 an explicit when-to-use ('authenticated seller wants to poll their listing before deciding to accept or reject an offer'), a concrete example query, and explicit when-not ('Do not use for casual ticket buyers'), plus named alternatives (search_events, get_ticket_listings, accept_offer/reject_offer). Routing is unambiguous.

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