browser_stop_video

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

The description 'Stop video recording' implies a mutating action, but annotations declare readOnlyHint=true, which states no state modification. This is a direct contradiction. The description adds no behavioral insights beyond the annotation conflict.

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 sentence of three words, with no wasted content. It is front-loaded and maximally concise for the purpose conveyed.

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?

Despite the tool's simplicity, the description is incomplete due to the annotation contradiction. It fails to clarify actual behavior (e.g., whether it truly stops a recording or is a read-only operation). No output schema or further details exist to compensate.

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?

There are zero parameters, so the schema fully covers them. Baseline for 0 params is 4. The description does not need to add parameter info, and it does not misrepresent anything.

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 'Stop video recording' clearly states the action (stop) and the resource (video recording). It is distinct from sibling tools like browser_start_video and browser_video_chapter, providing a specific verb+resource pair.

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 guidance is provided on when to use this tool versus alternatives. It does not mention prerequisites (e.g., video must be recording) or when not to use it. The context is purely implicit.

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