seatgeek_search_venues

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

With no annotations, the description should fully disclose behavior such as authentication (api_key), rate limits, or response format. It does none of this, simply stating 'Search for venues on SeatGeek' without any behavioral context.

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 extremely concise at 4 words, but it is under-specified. Conciseness should not come at the cost of completeness; every word should earn its place, but here it fails to provide necessary details.

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 and zero schema coverage, the description must explain the result format (e.g., list of venues) and how to use the parameters. It is completely inadequate for a tool that requires user input and returns data.

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%, and the description adds no meaning to the parameters 'q' and 'api_key'. The agent receives no hints about what 'q' should contain or how to provide the API key.

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 verb 'Search' and resource 'venues' on 'SeatGeek', distinguishing it from sibling tools like seatgeek_get_venue and seatgeek_search_events. However, it does not specify what the search query 'q' represents (e.g., name, location), leaving some ambiguity.

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?

No guidance is provided on when to use this tool vs alternatives like seatgeek_get_venue for a specific venue. The description does not mention prerequisites or context for searching venues.

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