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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false. The description adds valuable context: results are 'upcoming' (time-bounded), returns only ticket inventory, and prices are estimates subject to change at checkout. This goes beyond what annotations provide, though it does not describe pagination or ordering behavior.

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?

The description is compact yet comprehensive, covering purpose, coverage, filters, return type, alternative, and a pricing caveat in a few sentences. It is front-loaded with the core purpose and well-organized, though slightly long for a tool description.

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 explains what is returned (event inventory, tickets only) and flags the price uncertainty. It also points to search_packages for fuller packages. Missing details like pagination or default limit are minor given the tool's simplicity and the presence of limit in the schema. It is sufficiently complete for an agent to call it correctly.

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 must compensate. It names the filter dimensions (sport, city, country, date range), which covers most parameters, but omits limit and currency. It does not explain the meaning of each parameter individually, leaving those two to the schema alone. The high-level filter mention is helpful but not exhaustive.

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?

The description clearly states the tool searches upcoming sporting and music events bookable on Event Escapes. It enumerates the sports covered and explicitly differentiates from search_packages by noting this returns tickets only while packages are handled elsewhere. This distinguishes it from siblings like get_event_details and search_experiences.

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?

The description gives direct guidance on when to use this tool (for tickets) and explicitly names search_packages as the alternative for curated packages. It also mentions filters and the estimate-vs-final-price caveat. It does not mention other siblings like search_experiences or search_hotels_near_event, but the primary alternative is covered clearly.

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