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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuine value by clarifying that pricing is an aggregate snapshot only (no per-seat rows) and that there is no checkout/purchase flow, telling the agent what it cannot do. No auth/rate-limit details, but the added constraints are meaningful.

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?

Three tight sentences, front-loaded with the returned content, then the id source, then the pricing caveat. Every sentence carries information and nothing is wasted.

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?

Although an output schema exists (so return values needn't be explained), the description still usefully frames them and, importantly, sets expectations about the aggregate-only pricing and absent purchase flow. For a single-event detail tool with one required param, nothing an agent needs 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% and the single id parameter is already documented in the schema. The description adds meaning beyond the schema by disclosing the origin of the id (seatgeek_search or seatgeek_performer_events), which is not present in the structured field.

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 resource ('One SeatGeek event's full detail') and enumerates exactly what is returned (title, timing, venue, performers, category taxonomy, pricing snapshot). This clearly distinguishes it from the sibling search/list tools (seatgeek_search, seatgeek_events_near, seatgeek_performer_events) as a single-event detail fetch.

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 tells the agent where the required id comes from ('obtained from seatgeek_search or seatgeek_performer_events'), which is actionable routing guidance, and draws a boundary ('no checkout/purchase flow'). It stops short of an explicit when-to-use-vs-alternative statement, but the context is clear.

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