obs-toggle-replay-buffer

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions toggling but doesn't explain what that entails—whether it starts/stops the buffer, requires specific permissions, has side effects, or what the expected outcome is. This leaves significant gaps in understanding the tool's behavior.

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, efficient sentence that directly states the tool's action without any wasted words. It's front-loaded and appropriately sized for a simple toggle function.

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 complexity of toggling a replay buffer (a state-changing operation) and the lack of annotations and output schema, the description is incomplete. It doesn't cover behavioral aspects like what 'toggles' means in practice, potential errors, or the result of the action, making it inadequate for safe use.

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 0 parameters, and schema description coverage is 100%, so no parameter information is needed. The description appropriately doesn't discuss parameters, earning a high baseline score for not adding unnecessary details.

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 clearly states the verb ('toggles') and resource ('state of the replay buffer output'), making the purpose specific and understandable. However, it doesn't differentiate from sibling tools like 'obs-start-replay-buffer' or 'obs-stop-replay-buffer', which would require explicit comparison for a perfect score.

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 is provided on when to use this tool versus alternatives like 'obs-start-replay-buffer' or 'obs-stop-replay-buffer'. The description lacks context about prerequisites, such as whether the replay buffer must be configured or running, leaving usage unclear.

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