obs-resume-record

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

No annotations are provided, so the description must fully disclose behavior. It states 'Resumes the record output', implying a mutation that resumes recording, but doesn't cover critical aspects like side effects (e.g., if recording isn't paused), permissions, error conditions, or what happens if invoked incorrectly. This leaves significant gaps in understanding the tool's operation.

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 no wasted words, making it efficient and front-loaded. However, it could be slightly more informative without losing conciseness, such as by clarifying 'record output' in the context of OBS, but it's still well-structured.

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 tool's complexity (a mutation with no annotations and no output schema), the description is insufficient. It lacks details on behavior, usage context, and potential outcomes, making it incomplete for safe and effective use. Without annotations or output schema, more descriptive content is needed to cover operational nuances.

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 documentation is needed. The description doesn't add parameter details, which is appropriate, but it also doesn't compensate for any gaps—though none exist. A baseline of 4 is applied since no parameters are present, and the description doesn't introduce confusion.

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 'Resumes the record output' specifies the action (resumes) and target (record output), which clarifies the tool's purpose. However, it's somewhat vague—'record output' could refer to recording in OBS, but it doesn't explicitly distinguish this from sibling tools like 'obs-start-record' or 'obs-toggle-record-pause', leaving room for ambiguity.

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. Given siblings like 'obs-pause-record', 'obs-toggle-record-pause', and 'obs-start-record', the description lacks context for selection, such as prerequisites (e.g., recording must be paused) or timing, which could lead to misuse.

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