obsbot_tail2_gesture

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

With no annotations, the description carries the full load; it does disclose the read/write duality, that writes are readback-verified, and the provenance of the measurements. It omits conflict/precedence rules between zoom and zoomFactor, required permissions, and what happens on a failed write.

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: the read/set mode and affected fields come first, then a concrete example value, then the optionality and verification note. No filler, and the provenance tag is compact.

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 5-parameter, zero-coverage, annotation-free tool with no output schema, the description covers most of what an agent needs but leaves the `camera` parameter undocumented and gives no defaults or failure behavior. Adequate but with clear gaps.

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, and it defines four of five parameters including the meaning of zoomFactor ("multiplier one zoom gesture applies, e.g. 2.0"), which the schema only bounds numerically. However the `camera` parameter is left entirely unexplained in both schema and description.

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/set) and a specific resource (gesture-control switches and gesture zoom factor), with the individual fields named. It is clearly distinguishable from generic zoom siblings like obsbot_tail2_zoom or obsbot_tail2_hybrid_zoom, though it never explicitly contrasts itself with them.

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?

"Read (bare) or set..." implies that calling with no arguments reads and passing fields writes, and "each field is optional" reinforces that. There is no explicit statement of when to prefer this over sibling gesture/zoom tools, nor any prerequisites such as device wake state.

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