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 genuinely useful behavior beyond that: it returns exactly one page (pagination is the caller's concern), results are sorted soonest-first, and it mirrors the call behind SeatGeek's own city/homepage sections, which tells the agent what result shape/quality to expect.

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, zero filler, and the core scoping facts (one page, near coordinate, soonest first) are front-loaded before the sibling cross-reference.

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 4-parameter read-only geo query with an output schema present, the description covers purpose, ordering, pagination semantics, and input sourcing. Return-value details are correctly left to the output schema; only minor gaps remain (no radius semantics, no note on what 'near' resolves to).

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% (lat, lon, page, per_page all documented with defaults and range), so the schema carries the parameter burden. The description only reinforces that any coordinate may be passed directly; it adds no format or edge-case detail beyond that, which is the correct baseline 3 when the schema is complete.

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+scope: 'One page of SeatGeek events near a coordinate, soonest first.' The scope qualifiers (single page, geo-anchored, sorted by date) differentiate it clearly from siblings like seatgeek_events_by_category, seatgeek_venue_events, and seatgeek_search without needing to open any schema.

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?

Explicitly routes the agent: 'Pair with seatgeek_cities for a curated list of coordinates, or pass any coordinate directly.' That is clear positive guidance on how to source inputs, though it stops short of stating when this tool should be preferred over the other event-listing siblings (e.g. category or venue scoped calls).

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