Start Stream

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

The description adds no behavioral context beyond what the annotations already state. Annotations indicate readOnly=false, idempotent=false, and openWorld=true, but the description does not clarify what side effects occur, whether starting an already-active stream errors, or what happens to the streaming session. It simply restates the action without additional disclosure.

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 a single short sentence with no wasted words or filler. However, it largely duplicates the tool name and title, adding minimal new information, so it is concise but somewhat redundant rather than exemplarily informative.

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?

The tool is simple with no parameters, no output schema, and annotations covering basic safety traits, so a short description can be adequate. Yet the description omits any guidance about preconditions (e.g., OBS connection, stream configuration) or the non-idempotent nature of the action, leaving the agent to infer important operational context from the tool name alone.

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 input schema is empty, so the description is not required to explain parameter semantics. The baseline for a zero-parameter tool is 4, and the description does not need to compensate for any schema gaps.

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 'Start streaming in OBS' clearly states the specific action (start) and resource (streaming), leaving no ambiguity about the tool's core purpose. It distinguishes from siblings like obs-stop-stream, obs-toggle-stream, and obs-start-record by naming the exact operation.

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 no guidance on when to use this tool versus alternatives such as obs-toggle-stream or obs-start-record. There is no mention of prerequisites, such as requiring OBS to be connected or already configured, nor any indication that this tool may fail if already streaming.

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