Stop stream

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

With no annotations provided, the description carries the burden. It discloses that the action ends the broadcast for all viewers (high impact) and that confirmation is required. This is significant behavioral context for a destructive operation, though it doesn't describe the response or reversibility.

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, front-loaded with the action and a concise warning. Every word adds value, with 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 tool with one parameter and an output schema, the description covers purpose, impact, and user confirmation requirement. It is complete enough for an agent to invoke correctly without further guidance.

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 only defines 'confirm' as a boolean with default false. The description adds meaning by stating that explicit user confirmation is required, directly explaining the purpose of the 'confirm' parameter. This compensates for the 0% schema description coverage.

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 'Stop the live stream' with a specific verb and resource. It distinguishes this from sibling tools like 'stop_recording' or 'pause_recording' by explicitly naming the stream as the target.

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 provides clear context: it is used to end a broadcast, and it emphasizes that explicit user confirmation is required before calling. It doesn't explicitly mention when not to use or name alternatives, but the warning about high impact gives strong usage guidance.

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