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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds real context beyond them: it requires auth, requires read:bids scope, and notes the data is a live row from the connected resale + primary offer book. It does not discuss staleness or rate limits, but with an output schema present the return format is covered elsewhere.

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?

Front-loads provenance and purpose, then usage and alternatives. Mostly every sentence earns its place; the 'casual ticket buyers' sentence is slightly verbose but serves a genuine routing purpose.

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 explained, and annotations carry the safety profile. Combined with auth/scope requirements, trigger conditions, and sibling routing, an agent has everything needed to invoke correctly.

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% and the single parameter is documented in the schema as a public listing identifier from list_open_listings. The description says 'identifier is in hand' but adds no format or validation detail beyond the schema, so the 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: retrieve the full record for one open listing, and clarifies the scope is a single row from the live offer book. It explicitly contrasts with list_open_listings (list) and get_ticket_listings (standard inventory), so an agent can separate it from siblings without opening a 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 the trigger condition ('a listing identifier is in hand', before making an offer), an explicit exclusion ('do not use for casual ticket buyers; seller-side and power-user surface'), and names the alternatives ('search_events', 'get_ticket_listings') for standard purchases. When/when-not/alternatives are all present.

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