obs-toggle-record-pause

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

With no annotations, the description carries full burden but only states the action ('toggles pause') without disclosing behavioral traits like side effects (e.g., whether it affects file output, requires specific permissions, or has rate limits). It doesn't explain what happens on toggle (e.g., pauses if recording, resumes if paused), making it insufficient for a mutation tool with zero annotation coverage.

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, direct sentence with zero waste—'Toggles pause on the record output'—front-loading the core action without unnecessary elaboration. It's appropriately sized for a simple toggle function with no parameters.

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 is incomplete: it lacks details on behavior (e.g., state changes, effects), error conditions, or return values. Given the complexity of toggling a recording state in OBS, more context is needed to guide effective use, making it inadequate despite the concise phrasing.

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 with 100% schema description coverage, so no parameter details are needed. The description doesn't add param semantics, but this is acceptable given the baseline; it avoids redundancy, earning a score slightly above the minimum viable due to efficient handling of the no-param case.

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 'Toggles pause on the record output' clearly states the action (toggle) and target (record output), distinguishing it from siblings like 'obs-pause-record' and 'obs-resume-record' by implying a state-switching behavior. However, it doesn't specify what 'record output' refers to (e.g., OBS recording), leaving some ambiguity compared to more explicit alternatives.

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 guidance on when to use this tool versus alternatives like 'obs-pause-record' or 'obs-resume-record' is provided. The description implies a toggle action but doesn't clarify prerequisites (e.g., requires recording to be active) or contextual constraints, leaving usage decisions to inference.

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