Pause Recording

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

Annotations already indicate readOnlyHint=false, destructiveHint=false, and idempotentHint=true. The description does not contradict these and adds minimal behavioral context (e.g., what happens if already paused or not recording). It doesn't enrich beyond the annotations, which is acceptable for a simple action, but no extra insight is provided.

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, clear sentence with no wasted words. It is appropriately sized for the tool's simplicity and delivers the core meaning immediately.

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?

With no parameters, no output schema, and a straightforward single-action behavior, the one-sentence description is complete enough for an agent to invoke the tool correctly. The context is low-complexity, so no further explanation is required.

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, so there is no schema detail to clarify. The baseline for zero parameters is 4, and the description doesn't need to explain any parameter semantics.

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 'Pauses the record output' uses a specific verb and identifies the resource ('record output'). It clearly distinguishes itself from siblings like obs-resume-record and obs-toggle-record-pause, whose names and descriptions would imply opposite or combined actions.

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 relative to alternatives, such as obs-toggle-record-pause or obs-resume-record. No exclusions, prerequisites, or context are given; the agent is left to infer usage solely from the name and description.

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