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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safe-read profile is covered. The description adds a genuinely useful behavioral note that any of the three result lists may come back empty for a non-matching type, which is comparable in value to the scoping constraint credited in the calibration example — solid, but not rich.

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?

Two sentences, front-loaded with the primary function before the empty-results caveat. No filler, though the 'same call the site's search box uses' clause is more flavor than actionable detail.

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 the description covers catalog scope and the empty-list behavior. Given a simple 2-param read tool with full annotation and schema coverage, this is nearly complete, missing only explicit alternates to the sibling lookup tools.

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 both `q` and `limit` (range, default) are fully documented in the schema. The description adds no parameter-level syntax or format detail beyond that, 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 (free-text search) and resource (events, performers, venues in SeatGeek's catalog), and even notes it mirrors the site's own search box. It doesn't explicitly name the sibling lookup tools (seatgeek_event, seatgeek_performer, seatgeek_venue), so differentiation relies on scope inference, but the purpose is unambiguous.

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?

Usage is implied: reach for this when you have a free-text query rather than a known ID. There is no explicit when-to-use/when-not, no mention of the specific-ID siblings, and no prerequisites or edge-case routing guidance, so an agent must infer the alternative.

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