Stop recording

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description adds meaningful context beyond them: the tool only acts during an active recording, requires confirmLive=true, and returns the file path (valuable since no output schema exists). It does not state what happens on failure or whether the file is finalized, but the behavioral profile is well covered.

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?

Three short sentences, front-loaded with the action and its result, followed by the precondition and the default. The parenthetical '(it only acts while recording)' earns its place by explaining why confirmLive is mandatory.

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 destructive two-parameter tool with no output schema, the description covers the action, the precondition, the dry-run default, and the return value. Only minor gaps remain, such as error behavior when no recording is active.

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 100%, so both parameters are already documented, including the dry_run default and the confirmLive requirement. The description restates 'dry_run by default' and 'needs confirmLive=true' without adding syntax or edge-case meaning, so the baseline 3 applies.

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 names a specific verb and resource ('Stops the main OBS recording') and adds the return value ('returns the file path'), so the agent knows exactly what happens. It does not explicitly name start_record as the counterpart, but the stop/start pairing is unambiguous from the verb alone.

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 states a real precondition: 'it only acts while recording' and that confirmLive=true is always needed, which tells the agent when this call will actually do something. There is no explicit 'when not to use' or alternative routing, but the operating condition is clear.

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