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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful behavioral context beyond that: results are upcoming events only and sorted soonest-first, which tells the agent how to interpret ordering. Pagination is left implicit but is documented in the schema.

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 tight sentences with zero filler. The scope/ordering clause is front-loaded, and the second sentence delivers the id-provenance hint. Every clause earns its place.

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?

With an output schema present, return values need not be explained, and annotations cover the safety profile. The description covers resource, scope, ordering, and id provenance, leaving only minor gaps like explicit pagination behavior, which the schema already provides.

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 the schema already explains page, per_page, and venue_id. The description largely restates the venue_id meaning and adds only light provenance guidance ('obtained from a search or event result'), so 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+resource: returns a paginated list of a SeatGeek venue's upcoming events, with ordering ('soonest first') and page scope. An agent can identify the resource clearly, though it does not explicitly contrast itself with siblings like seatgeek_venue (details) or seatgeek_search.

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 implies the prerequisite workflow by saying venue_id is 'obtained from a search or event result,' which signals you need a venue id first. However, it never names the alternative tools (seatgeek_search, seatgeek_venue) or states when to prefer this over seatgeek_events_near or performer_events.

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