stubhub_search

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

With no annotations, the description carries the burden. It discloses that the endpoint is anonymous, uses multipart form data, requires no cookies or CSRF token, and returns results in StubHub's own performer/grouping/event groups. This adds valuable behavioral context beyond a basic search tool, though it omits pagination or error 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 two sentences with no redundancy. The first sentence states the purpose, and the second adds essential implementation details. It is front-loaded and every sentence earns its place.

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 simple search tool with one parameter and no output schema, the description is fairly complete: it explains what is searched, the result grouping, and the technical nature of the request. It doesn't cover pagination or result size, but that is not critical for a search tool.

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?

The input schema already documents the single 'query' parameter with description 'Search query' (100% coverage). The description does not add any additional meaning about query format, length, or examples, so it adds no value beyond the schema. Baseline 3 applies.

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 the resource 'StubHub for performers, events, and groupings,' making the purpose explicit. It also distinguishes itself from other StubHub tools by mentioning the anonymous grouped-search endpoint and result grouping, which helps differentiate from sibling tools like stubhub_performer_events or stubhub_trending.

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 implies usage for general search across performers, events, and groupings but does not explicitly mention when to use this tool versus alternatives like stubhub_performer_events for a known performer. It lacks exclusions or explicit routing guidance, so an agent must infer usage context.

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