obsbot_tail2_usb_mode

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

With no annotations, the description carries the full burden, and it does contribute real behavioral context: remote safety of switching, network-based control path, and a readback-verified write. However it omits permission/auth requirements, what happens on failure, and any latency or disconnection risk, which matters for a mode switch that could drop the UVC stream.

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 tight sentences, front-loaded with the action and valid values. The measurement-date parenthetical is slightly opaque but short enough to be tolerable.

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?

No output schema exists, so the description should clarify what a read returns, and with no annotations and 0% schema coverage, the `camera` parameter and the omitted-mode read behavior are gaps. It is adequate but leaves an agent guessing on read semantics and targeting.

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%, so the description must compensate. It usefully explains the mtp/uvc value semantics ('measured wire value' vs 'presumed counterpart') and the measurement provenance, but the second parameter `camera` is never mentioned, leaving half the inputs undocumented.

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 pair (read or set) and resource (USB-C function mode), and enumerates the two valid values. It is distinguishable from siblings, but doesn't explicitly contrast with any of them or state the read-vs-write default when `mode` is omitted.

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?

There is no when-to-use guidance or alternative routing. The note 'Control rides the network either way, so switching is safe remotely' is a safety reassurance, not a usage condition, and nothing tells the agent how this differs from obsbot_tail2_stream or other connection-related siblings.

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