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

Annotations already cover the read-only, non-destructive, open-world profile, and the description goes further by explaining the dual-sided order book semantics, fee-inclusive pricing, and ask-side availability. It doesn't mention rate limits or result cap behavior, but the added output-context is valuable beyond the annotations.

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-loaded with the usage condition, then the return content, then the routing guidance and exclusion. Every sentence earns its place, though the third clause is fairly dense and slightly redundant with the opening 'might make an offer' phrasing.

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-value documentation isn't required, and the description still summarizes the payload well. Annotations cover safety, so nothing critical is missing for correct invocation.

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 each parameter (cbsa, genre, limit, query, min/max_date) is already documented in the schema. The description adds no per-parameter meaning beyond what the schema provides, 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?

The description states a specific action (searches XP events) and precisely what it returns (both sides of the connected order book, fee-inclusive get-in price, whether fans are selling with cheapest ask). It is immediately distinguishable from the sibling search_events tool.

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?

Explicit trigger ('when the user is shopping and might make an offer rather than pay asking price'), a named preferred alternative ('Prefer this over search_events whenever price matters'), concrete examples, and an explicit exclusion ('Do not use for scores, news, or standings').

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