obs-toggle-stream

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

With no annotations, the description carries the full behavioral burden and discloses almost nothing: it does not say whether the call is idempotent, what happens if OBS is disconnected or the stream is in a transitional state, or what the resulting state/response is. It also omits any mention of the confirmation gate that the schema's `confirm` parameter implies under OBS_PROTECT_DESTRUCTIVE.

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?

A single front-loaded sentence with no filler or redundancy. Its brevity is clean, though the resulting definition is thin for a state-changing operation.

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 mutation tool with no annotations and no output schema, the description should explain the state transition and the confirmation requirement. As written it leaves the agent guessing about the outcome and about when the protected-mode confirmation applies.

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 100% for the single optional `confirm` parameter, so the schema already explains it. The description adds no meaning beyond that, which is the baseline 3 case for a one-parameter tool.

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 states a specific verb ("Toggle") and resource ("the streaming state in OBS"), so the operation is unambiguous. It does not distinguish itself from the closely related siblings obs-start-stream and obs-stop-stream, which is the only reason it falls short of 5.

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?

There is no when-to-use guidance at all — nothing says to prefer this over obs-start-stream/obs-stop-stream when the desired state is known, and nothing warns that toggling when already live will stop the stream. The agent must infer the semantics entirely from the name.

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