stubhub_trending

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

With no annotations, the description carries the behavioral burden. It discloses what each returned item contains (follower/favorites count and upcoming event date range) and explicitly states that a zero count with an empty performers list is a valid no-results response, which helps the agent avoid misclassifying empty results as errors.

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 short and front-loaded with the core action. There is slight redundancy between 'List ... trending performers' and 'Lists the performers/teams ...', but the additional details about return contents and the valid empty response earn their 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 tool with one optional parameter and no output schema, the description is largely complete: it identifies the data source, the returned fields, and the empty-response semantics. It does not explain sorting/ordering or enumerate the category IDs, but those are minor gaps for this endpoint.

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 only parameter at 100% coverage ('Filter to one top-level vertical'), so the baseline is 3. The description adds no further meaning about what the integer values 0-3 represent or how filtering affects the hero rotation, but it does not need to restate the schema.

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: 'List StubHub's currently-featured trending performers' and clarifies the exact source as the homepage hero rotation. By specifying performers/teams rather than events, it distinguishes itself from sibling event-oriented tools like stubhub_trending_events even without naming them.

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 intended context is clear enough: use this tool when you need the performers/teams StubHub is currently featuring on its homepage, optionally filtered by a top-level category. However, it provides no explicit when-not-to-use guidance or alternatives such as stubhub_trending_events, so the agent must infer the right sibling.

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