seatgeek_search_performers

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: no mention of result limits, pagination, fuzzy vs exact matching, or how the api_key is used, which is where value could be added.

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?

One short, front-loaded sentence with no filler, but it is terse to the point of under-specification rather than genuinely efficient. Nothing is wasted, yet almost nothing is contributed either.

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?

For a two-parameter open-world search with no output schema, the description should at least say what 'q' matches against and roughly what comes back. With rich annotations covering safety but zero parameter documentation, an agent is left to infer how 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% and the description does not compensate. The required parameter 'q' is never explained (free-text name? partial match?), and 'api_key' is undocumented, so an agent must guess both the format and semantics of the query string.

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 names a specific verb ('Search') and resource ('performers on SeatGeek'), so an agent can tell this is a performer lookup rather than an event or venue lookup. It does not explicitly distinguish itself from the sibling seatgeek_get_performer, but the search/get distinction is clear from the names.

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?

There is no guidance on when to use this versus seatgeek_get_performer, seatgeek_search_events, or seatgeek_search_venues. The agent must infer that this is for discovering performers by name and that a follow-up get_performer call is needed for details.

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