seatgeek_search_events

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

Annotations already declare the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=true). The description adds essentially no behavior beyond that: it does not mention API-key requirements, pagination, rate limits, result ordering, or what happens when filters are omitted.

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 a single front-loaded sentence with no filler or repetition. It is structurally clean but so terse that it omits information an agent would need to use the tool correctly.

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?

For a five-parameter search tool with no output schema and no schema descriptions, the description is far too thin. Annotations cover the safety profile, but the definition leaves out parameter meaning, pagination behavior, authentication expectations, and return-value characteristics.

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 0%, and the description does not explain any of the five parameters. It does not clarify the query field q, the item type filter, the api_key requirement, per_page pagination, or the datetime_utc_gte filter.

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 gives a specific verb ('Search') and resource ('events') and names the provider ('SeatGeek'), so an agent can tell it is an event search operation. It does not, however, differentiate it from sibling searches such as tm_search_events, eventbrite_search_events, or seatgeek_get_event.

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?

The description states only what the tool does, with no guidance on when to use it versus alternatives like seatgeek_get_event, seatgeek_search_venues, or other event-search tools. It includes no exclusions, prerequisites, or examples of suitable queries.

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