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

No annotations provided; the description carries full burden. It discloses that results are returned most imminent first, each with a booking link and gig-page URL, that gigstamp does not sell tickets, and that coverage aims to be complete with grassroots emphasis. No contradictions.

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 a single long paragraph that front-loads the main action and filters. It includes some verbose examples and parenthetical notes, but overall is efficient and well-structured.

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?

Given 9 parameters, no output schema, and sibling tools, the description covers input filtering, output format (ordering, booking link, gig-page URL), and constraints (only supported cities). It addresses the tool's scope adequately.

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 high (89%), so baseline is 3. The description summarizes available filters (date range, venue, category, scale, free text) but does not add significant detail beyond what the schema already provides for individual parameters.

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 a supported city's upcoming live music and events, enumerates event types, and lists filtering options. It distinguishes from siblings like get_gig (single gig) and list_cities (supported cities).

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 provides guidance on when to use the tool: for searching events in supported cities, and references list_cities to check supported cities. It mentions filtering options and default ordering, but does not explicitly state when not to use it.

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