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

Annotations already declare this is a safe read (readOnlyHint, idempotentHint, non-destructive), so the description is free to add the traits that matter: result ordering (soonest first), that all filters are optional and combine freely, that the response includes ticket counts and starting prices, and the critical constraint that there is no pagination beyond 'limit' (default 10, max 50). The no-pagination caveat is exactly the kind of behavior an agent would otherwise discover only by failure.

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?

Three sentences, front-loaded with the "start here" signal, then capability, then result behavior and routing. No restatement of the title and every clause carries information an agent can act on.

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?

There is no output schema, and the description compensates by describing what comes back (events, ticket counts, starting prices) and in what order. Combined with the safety annotations and complete parameter coverage, an agent has everything needed to call this correctly on the first try.

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 coverage is 100% and each parameter is documented with format hints (ISO dates, city examples, enum for category), so the schema carries the load. The description adds value beyond it by stating that all filters are optional and combine freely, which is not explicit in the schema, plus restating the limit semantics with the consequence (no further pages).

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?

Specific verb+resource ("search FrontRowTickets.com ticket inventory") with the dimensions it searches over (free text, city, date range, category) and the categories enumerated. It is clearly distinguishable from get_event and get_deals, which are named in the same description.

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?

"Start here for discovery" positions it as the entry point, and the final sentence routes to alternatives with conditions: get_event for a single event's full record, get_deals when there is a hard budget cap. Both when-to-use-this and when-to-use-siblings are explicit.

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