Start recording

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds meaningful behavior beyond them: the tool is dry-run by default and requires an explicit confirmLive override when OBS is streaming or recording. That guard detail is exactly the kind of risk context an agent needs before mutating state.

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?

Two short sentences, front-loaded with what it does and then the guard constraint. No filler, and the parenthetical scope note is genuinely informative rather than restating the name.

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 two-param mutation with no output schema and annotations covering the destructive profile, the description supplies the guard behavior an agent needs to invoke it safely. It doesn't mention return values or failure modes, but those are largely covered by the schema defaults and annotations.

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 coverage is 100% and both parameters are self-documenting, so the baseline is 3. The description restates the dry_run default and the confirmLive condition rather than adding format, interaction, or side-effect semantics the schema lacks.

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?

States a specific verb and resource (starts the main OBS recording) and adds the Source Record filter side effect, so the agent can distinguish it from stop_record and check_source_record without opening a schema.

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?

Explains the guard model ('dry_run by default; needs confirmLive=true while streaming'), which tells the agent the precondition for actually applying the change. It does not name a sibling alternative or say when to prefer check_source_record first, so it stops short of full when/when-not routing.

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