obsbot_tail2_gimbal_position

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

With no annotations, the description carries the full burden and does so thoroughly: it discloses the non-obvious implementation (save → read → delete preset), the ~2s latency, the irreversible-overwrite hazard for an occupied slot, and that stale 'pose-probe' slots are cleaned rather than trusted. These are exactly the side effects and risks an agent needs before invoking.

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 dense sentences, front-loaded with the returned values, then the mechanism, then the constraint. No sentence is filler — the implementation detail is what justifies the constraint that follows.

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, and the description compensates by naming the return fields and units (degrees; zoom ratio). It also covers the side-effect profile and latency, so an agent can call it correctly and know what to expect.

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 is one parameter ('camera') with 0% schema description coverage, and the description never mentions it — not its format, whether it names a device, or whether it is optional. The baseline-4 exemption applies to zero-parameter tools, and this exceeds that; the description fails to compensate for the coverage gap.

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 and resource ('read the Tail 2's live gimbal pose in degrees (yaw/pitch/roll) plus the zoom ratio'), which is distinct from the sibling gimbal-move/preset tools. An agent knows exactly what it gets back without opening the 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?

Explains the context that forces this tool's use ('the API has no direct pose read') and states the precondition (at least one empty preset slot). It does not explicitly name a sibling alternative or a when-not condition, but the usage context is clear.

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