start_stream

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

With no annotations, the description carries the full burden. It discloses a prerequisite (settings must be configured) but does not explain what happens if the prerequisite is unmet, failure modes, or side effects of starting a stream. Minimal behavioral disclosure beyond the prerequisite.

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, containing only two sentences with no wasted words. It front-loads the core action ('Go live') and adds one essential prerequisite, making it easy to scan and understand.

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 zero-parameter, no-output-schema tool, the description covers the essential purpose and a key prerequisite. However, it does not mention what a successful start returns or what errors might occur (e.g., already streaming, not configured), which could be valuable for an agent deciding whether to invoke it.

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 tool has zero parameters, and the schema is trivially complete. Per the baseline for 0 params, the description does not need to add parameter details. It does mention the required configuration, which indirectly relates to encoding/stream settings but no parameter semantics are needed.

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 'Go live' clearly indicates starting the stream output, with an explicit prerequisite. It distinguishes from siblings like stop_stream and toggle_stream by emphasizing the start action, though 'Go live' is somewhat informal.

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 a clear context for use: requires stream service settings to be configured first, and references the appropriate configuration tool. However, it does not explicitly state when not to use this tool or mention alternatives like toggle_stream.

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