streamlabs_toggle_recording

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

With no annotations, the description carries the burden of behavioral disclosure. 'Start or stop' clearly communicates the two possible outcomes of a toggle, but it does not specify how the current state is determined or any side effects beyond starting/stopping. This is adequate for a simple zero-parameter toggle.

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 concise sentence, front-loaded with the core action, and contains no redundant information. It efficiently conveys the tool's purpose.

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 toggle without an output schema, the description sufficiently covers the essential behavior. However, it leaves room for interpretation about whether 'local recording' means something distinct from streaming or replay buffer, though the naming partially addresses this.

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 schema coverage is 100%, so the description does not need to explain parameters. The baseline for zero parameters is 4, and no additional parameter info is necessary.

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 or stop local recording.' uses a specific verb and resource, clearly indicating a toggle action on local recording. It distinguishes from siblings like streamlabs_toggle_streaming and replay buffer tools by specifying 'local recording'.

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 explicit when-to-use or alternatives are mentioned. The implied usage is that this tool manages local recording, but it does not differentiate from streaming or replay buffer tools, which are present in sibling tools.

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