obsbot_tail2_hybrid_zoom

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

With no annotations, the description carries the full behavioral burden and delivers exceptional detail: the tool speaks a private UDP 9999 protocol, returns settled:false if readback hasn't caught up, performs a behavioral double-check via obsbot_tail2_zoom ratio 6.0, works with OBSBOT Center closed, and has been hardware-verified in both directions.

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?

Front-loads the purpose well, but the description is dense and includes implementation provenance (checksums decoded, byte-for-byte reproduction, hardware verification date) that is extraneous for an agent selecting and invoking the tool. The core information could be conveyed in half the length.

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 tool with no annotations, no output schema, and 0% schema description coverage, the description must compensate for parameter and return-value gaps. It richly covers behavior but says nothing about what the 'enabled' and 'camera' parameters do, leaving an agent unable to invoke it correctly without guessing.

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% and the description never mentions the 'enabled' boolean or the 'camera' string parameter. The phrase 'Unlock (or re-lock)' hints at a boolean toggle, but there is no explicit mapping to parameter values, and the 'camera' parameter is completely unexplained.

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 ('Unlock (or re-lock)') and resource ('hybrid digital zoom') and explains its unique purpose relative to the camera's normal REST API ceiling. Does not explicitly name sibling tools, but the contrast with 'PUT ptz/zoom above 5.0 is acknowledged but silently pins at 5.0' implicitly differentiates it from ordinary zoom tools.

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?

Provides clear context for when to use: to access the 5–12x digital region that OBSBOT Center normally unlocks via its private protocol, and notes it works with Center closed. No explicit when-not or named alternatives, but the context of the 5x ceiling is sufficient to infer applicability.

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