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

Annotations already declare this read-only and non-destructive, and the description goes further by disclosing conditional output behavior: generated-vs-organizer descriptions, predicted_end_time only when needed, ticket_offer only when fresh, and rank semantics. This substantially helps an agent interpret responses.

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 purpose is front-loaded and every sentence carries information: location scope, optional filters, output-field caveats, and the city/coordinates usage note. The detail is dense but necessary and there is no filler.

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 carries the burden of explaining return values, and it does so well by detailing description, lineup, rank, predicted_end_time, and ticket_offer. It does not specify result ordering, pagination, or the full event object, which keeps it from a 5.

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%, so the baseline is 3, but the description adds meaningful usage semantics by indicating that location can be supplied as a city or as coordinates, and by characterizing all non-location inputs as optional filters. This clarifies the relationship between city, latitude/longitude, and radius_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?

Description opens with a specific action and resource ('Search for events near a location') and clarifies it is for finding events in a city or near coordinates. It is clearly distinct from sibling search tools like search_artists, search_organizers, and search_event_weeks.

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 explicitly states when to use the tool: 'Use this to help users find events in a city or near coordinates.' It does not explicitly mention alternatives or when not to use it, so it earns a 4 rather than a 5.

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