obsbot_capture_record

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

With no annotations, the description carries full disclosure burden and does it well: it reveals the 60-minute auto-stop for open-ended recordings, that audio is on by default from the OBSBOT mic, the cross-platform outputPath default including the macOS quirk, and the returned sessionId. These are exactly the non-obvious behaviors an agent needs before invoking.

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 dense but front-loaded: the core action is in the first clause, and the parenthetical defaults and platform caveat come after. Some punctuation is run-on, but each clause adds operational value rather than filler.

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 tool with no annotations and no output schema, this covers the essentials: what it does, defaults, limits, prerequisite focusing step, and return value. An agent could invoke it correctly and know what to expect and how to stop it afterward.

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?

Schema description coverage is 0%, and the description compensates by explaining durationSec's open-ended behavior, audio's default and source, outputPath's default location, and the source enum values. Only 'source' semantics are thin beyond the enum list, but the schema already enumerates valid values.

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 opens with a specific verb and object: 'Start recording the camera to an MP4', which clearly distinguishes it from sibling capture tools like obsbot_capture_snapshot or obsbot_capture_preview. It also grounds the tool's role by noting it returns a sessionId used by obsbot_capture_stop, making its place in the workflow explicit.

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?

It gives a concrete precondition: ensure the camera is focused before calling, and names obsbot_focus_auto as the way to satisfy it, with an exception ('unless otherwise directed'). It doesn't explicitly contrast with alternatives (e.g., when to choose snapshot vs record), but the recording target and MP4 context make the intended situation clear.

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