stubhub_explore

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

With no annotations provided, the description carries the behavioral burden. It adds one genuinely useful behavioral disclosure: a zero count with an empty events list is a valid no-results response, which prevents an agent from misreading empty output as an error. It does not cover response shape, pagination, or error semantics, but the disclosure goes beyond what the name or schema convey.

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?

Three sentences and roughly 50 words, with no filler. The first sentence nearly restates the tool name and the second repeats it with filters, which is mild redundancy, but the valuable no-results edge case is included and the whole thing is compact.

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 an 8-parameter tool with no annotations and no output schema, the description is brief but adequate: it states function, scope, filters, and the empty-result edge case, and hints that the response contains a count and an events list. The main missing piece is routing among sibling event tools (stubhub_search, seatgeek_search, ticketmaster_search_events), which would materially improve completeness.

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 100%, so the baseline is 3 — the schema already documents formats, defaults, ranges, and known-good category ids for every parameter. The description's phrase 'optionally bounded by ticket price and by category' adds only a light semantic gloss over the price and category 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 names a specific verb and resource ('Discover StubHub events near a location') and adds a clear scope: a date range with optional ticket-price and category bounds. It reads clearly and avoids tautology, but it never explicitly distinguishes itself from sibling event-search tools such as stubhub_search, stubhub_venue_events, or seatgeek_search, so it stops short of a 5.

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 usage context is implied well enough — call this when you want StubHub events near a location within a date range — and the schema points to stubhub-categories for resolving category ids. However, there is no explicit when-to-use vs. alternatives guidance, no exclusions, and no mention of the many sibling discovery/search tools, which is a notable gap given the catalog.

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