obsbot_tail2_auto_zoom_speed

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

With no annotations, the description carries the full disclosure burden and does so substantially: it reveals the transport (UDP 9999, key 0x17), that there is no REST-readable state, no ack, and that the frame is synthesized and works even with Center closed. Only persistence/volatility of the setting across restarts is left unstated.

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 value, its range, and its purpose are front-loaded in the first clause, with the sibling distinction and transport details following. It is dense with useful specifics, though the parenthetical asides make it slightly packed.

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 raw UDP frame-control tool with no output schema, the description supplies the behavioral context an agent needs (transport, no-ack, no readable state). The only notable gap is the undocumented camera parameter.

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 coverage is 0%, so the description must compensate. It explains what speed controls and its range (though the 1-10 bounds already appear in the schema), but the camera parameter is left completely undocumented in both schema and description. Partial compensation justifies the baseline 3.

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 (Set) and resource (AUTO zoom speed), gives the range 1-10, and clarifies what the value controls (how fast AI-tracking auto-zoom framing moves). It explicitly distinguishes itself from the MANUAL speed on obsbot_tail2_zoom, so an agent can tell the two apart without opening a schema.

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 clearly differentiates this tool from its closest sibling (obsbot_tail2_zoom's speed param) and notes it works with Center closed, which frames usage context well. It does not, however, spell out an explicit when-to-use scenario or any prerequisites, so it stops short of a full 5.

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