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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds non-schema context: it requires auth and a read:bids scope, which an agent needs before calling. It does not discuss pagination behavior, though the output schema covers return shape.

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 the source and the core use case before the examples and exclusions. The example phrasing and the 'do not use' clause both carry routing value, though the sentence count is on the higher side for a list tool.

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 annotations covering the safety profile, a 100%-covered schema, and an output schema for returns, the description fills the remaining gaps: auth/scope prerequisites and the buyer-vs-seller decision boundary. An agent has everything needed to select and invoke it.

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 every filter, sort field, and the USDC raw-unit convention are already documented in the schema. The description only summarizes 'filterable by event, performer, and amount,' adding little beyond what the schema provides; 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 — browsing the live offer book of listings open on XP — and situates it in the resale + primary order book. This clearly separates it from the singular sibling get_open_listing and from the buyer-side search_events/get_ticket_listings.

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?

Explicitly gives trigger examples ('what's open near me this weekend'), names when NOT to use it (casual ticket buyers; this is the seller-side/power-user surface), and routes to two concrete alternatives with the condition that selects them.

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