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

Goes well past the readOnly/idempotent annotations: discloses sort order, that parking/tailgate events are appended after games, that an empty list can mean the search failed, and that the catalog carries no audience/vibe/popularity signals. It also explains price semantics (fees included, latest check, not a quote, null means none listed).

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?

Front-loads purpose and sort order, then walks parameters in a logical order. Slightly long with repeated illustrative examples, but the density is warranted by 12 undocumented parameters; nothing is truly redundant.

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?

No output schema exists, yet the description enumerates every returned field (eventId, name, venue, city, state, startsAt, fromAllInPrice, url) and explains the non-obvious ones plus the echoed place/performer and otherMatches. Minor gaps like page size and lat/lng interplay with radius don't impede correct invocation.

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?

With 0% schema description coverage across 12 parameters, the description does the entire job: it defines query vs performer vs near, spells out the full category enum and warns there is no generic 'concerts' value, maps natural-language dates ('this weekend', 'tonight') to ISO ranges, and clarifies max_price includes fees and radius defaults to 100 km.

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?

Opens with a precise verb+resource+scope: events on sale on UPFRONT across games, concerts, shows and comedy, sorted soonest first. The example queries anchor what it matches, and none of the siblings (best_seats, compare_prices, venue_info, etc.) overlap with catalog 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?

Gives concrete request patterns and comparative guidance ('performer is more exact than query for a team or artist'), plus default behavior ('*' means no text filter; without dates every upcoming date counts). It stops short of explicitly naming when to hand off to siblings like best_seats or compare_prices.

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