ebay_live_streams

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

With no annotations, the description carries the full burden. It states that the tool returns only currently live and upcoming streams (not past streams), which is useful behavioral context. It does not disclose pagination behavior or potential limitations, but the schema parameters for pagination provide some clues.

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?

Two short, focused sentences. The first gives the original action; the second adds necessary scope and constraint. No filler.

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 list tool with no output schema, this description is quite complete. It explains what is returned and the category constraint; the schema covers the optional parameters including pagination mechanics. It could mention the output format, but that is minor given the tool's simplicity.

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 schema already describes all three parameters clearly, including defaults and pagination semantics. The description only reinforces 'category channel' without adding meaning beyond the schema, so the baseline 3 is appropriate.

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 action ('List') and resource ('eBay Live streams') and adds a specific scope: only currently live and upcoming streams for a category channel. This differentiates it from the singular 'ebay_live_stream' and other related sibling tools, though it does not explicitly name 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 description implies clear usage for retrieving live/upcoming streams filtered by category channel. However, it does not explicitly mention alternatives like 'ebay_live_streams_batch' or 'ebay_live_stream_items' or provide when-not-to-use guidance, so it falls short of a full 5.

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