obs-stop-record

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

No annotations are provided, so the description carries full burden. It states the action ('stops') but doesn't disclose behavioral traits such as whether this is a destructive operation (likely yes, as stopping recording finalizes the file), if it requires specific permissions, or what happens if recording isn't active. 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, direct sentence ('Stops the record output') with no wasted words. It's front-loaded and efficiently conveys the core action, making it highly concise and well-structured for its 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?

Given the tool's complexity (a mutation operation to stop recording), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what 'record output' means, the effects of stopping (e.g., file saving, status changes), or error conditions, leaving the agent with insufficient context for reliable 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 documentation is needed. The description doesn't add parameter semantics, but this is acceptable given the lack of parameters, aligning with the baseline score of 4 for zero-parameter tools.

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 'Stops the record output' clearly states the action (stop) and target (record output), but it's somewhat vague about what 'record output' entails compared to siblings like 'obs-stop-stream' or 'obs-stop-output'. It distinguishes from 'obs-pause-record' by implying termination rather than pausing, but lacks specificity about the recording context.

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-toggle-record' or 'obs-pause-record' is provided. The description implies it should be used to stop recording, but it doesn't specify prerequisites (e.g., recording must be active) or contrast with similar tools, leaving usage context unclear.

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