stop_stream

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

No annotations present, so description must disclose behavior. It only states the core function but fails to mention side effects (e.g., stream stops, cannot be resumed), requirements, or the effect of the dry_run parameter. Lack of behavioral context beyond the obvious.

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 extremely concise (3 words), which is efficient but at the cost of missing critical information. It is front-loaded but lacks structure, offering no detail about parameters or behavior. Every sentence earns its place but should include more content.

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?

Given the tool has one parameter, no output schema, and no annotations, the description is far from complete. It fails to explain the dry_run parameter, any prerequisites (e.g., only works when streaming is active), or what the agent can expect (e.g., return value, state change). A single sentence is insufficient for safe invocation.

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 0%, meaning the input schema has no descriptions. The tool description does not mention the dry_run parameter at all, leaving its purpose and usage entirely unexplained. The agent must infer from the parameter name, which may be ambiguous (e.g., does dry run simulate stopping?).

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 'End the live stream.' clearly states the action (stop) and the resource (live stream), distinguishing it from related siblings like start_stream and stream_status. However, it does not elaborate on the scope or conditions, but the purpose is unambiguous.

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?

No guidance on when to use this tool versus alternatives (e.g., stop_record, disconnect). No mention of prerequisites (e.g., must have an active stream) or exclusions. The description assumes the agent knows when to invoke it.

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