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

Annotations already mark this as a safe, read-only, closed-world operation, so the description appropriately focuses on non-annotation traits. It adds the auth and read:bids scope requirement, explains that a 'large book' returns one page per lifecycle category with per-category pagination totals, and warns never to present a partial page as the whole set.

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 description is front-loaded with the pagination behavior and then moves to usage and alternatives, with no wasted sections. The 'large book' metaphor and some dense phrasing make it slightly less crisp than ideal, but every sentence carries actionable 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?

Given that an output schema exists and annotations cover safety, the description is complete enough to call correctly: it covers ownership scope, auth, pagination behavior, category bucketing, and the correct sibling alternatives. Nothing material for correct invocation 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%, so the baseline is 3. The description adds useful operational semantics beyond the schema by explaining how offset and state_category are intended to be used for paging or narrowing results, though it does not restate the per-category limit semantics.

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?

The description states a specific verb and resource: list an authenticated seller's own XP marketplace listings, bucketed by lifecycle category. It explicitly distinguishes this from buyer-facing siblings like list_open_listings, search_events, and get_ticket_listings, so an agent can choose correctly without opening another 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?

It gives concrete when-to-use examples ('show my tickets I'm selling', 'what's open in my seller queue') and names the alternatives for buyer browsing and buy-now flows. It also tells the agent what to do when has_more is set: disclose the partial page and either page with offset or narrow with state_category.

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