stop_virtual_cam

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only states the action without detailing side effects, idempotency, or prerequisites. For a mutation-like operation, this lacks important context such as what happens if the camera is already stopped or whether it affects other outputs.

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, front-loaded sentence that states the action and resource without any wasted words. It is as concise as possible while being clear.

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 simplicity (no parameters, no output schema), the description adequately defines the operation. The sibling context (start_virtual_cam, toggle_virtual_cam) helps ground the tool's role. However, it does not mention any return value or conditions, which slightly limits completeness.

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 zero parameters, so the description need not explain parameter meaning. The schema is empty, and the description is sufficient. Per instructions, 0 params warrant a baseline of 4.

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 clearly states the action (Stop) and the resource (virtual camera). It distinguishes itself from sibling tools like start_virtual_cam and toggle_virtual_cam by specifying exactly what it does.

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?

The description implies usage in the context of stopping the virtual camera, but it does not explicitly discuss when to use this tool versus alternatives like toggle_virtual_cam or start_virtual_cam. For a simple action, the purpose itself provides adequate guidance, but there is room for explicit alternatives.

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