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

Annotations already declare readOnlyHint and idempotentHint, but the description adds materially important caveats: fromAllInPrice is the last-checked page price, not a per-ticket-count quote, and null means no tickets listed rather than sold out. It also discloses ordering (soonest first), the 60-item cap, totalDates semantics, and the found/otherMatches disambiguation states.

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 the answer scope and example queries before parameter docs and return-field docs, so an agent can stop reading early. It is on the long side with some repetition around price semantics, but nearly every sentence adds a distinct constraint rather than restating the schema.

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 no output schema, the description fully specifies the response shape (eventId, name, venue, city, state, local start time, fromAllInPrice, url) plus the auxiliary fields tourGuide, artistPage, otherMatches and found. For an 8-parameter, annotation-light return surface, nothing an agent needs to call or interpret the result is missing.

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%, so the description carries the full burden and does: artist format with an example, near as a place name with radius default 150, lat/lng as a shared-location alternative, inclusive YYYY-MM-DD date bounds, and limit default 30 / max 60. Every one of the 8 parameters is given meaning the schema does not.

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 specific verb-and-resource statement ('An artist's upcoming dates on UPFRONT') plus the exact payload returned: dates, venues, cities, lowest all-in price per show, and tour guide. The three sample queries pin the resource and scope tightly enough to separate it from generic event search siblings like find_events or compare_prices.

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 trigger phrasings ('when is Olivia Rodrigo playing near Philadelphia?', 'cheapest Iron Maiden show this spring') and notes it handles shows across several cities, so an agent can pattern-match intent. It stops short of explicitly naming the siblings it supersedes (find_events, compare_prices) or stating when-not-to-use, which keeps it off a 5.

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