obsbot_gimbal_move

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

With no annotations, the description carries full burden. It discloses clamping ranges, direction conventions, and hardware verification. However, it omits error handling details and potential side effects (e.g., state changes).

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?

Two concise sentences: first defines action and conventions, second adds ranges and verification. No filler, well-structured.

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?

Despite missing parameter descriptions and no output schema, the description covers the core behavior adequately. Minor gaps like asynchronous completion or out-of-range behavior prevent a perfect score.

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 description must compensate. It explains yaw and pitch (ranges, direction) but does not mention the 'roll' and 'camera' parameters, leaving key semantics undefined.

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?

The description clearly states the action ('move the gimbal'), the resource (gimbal), and the mode ('absolute yaw/pitch angle'). It specifies direction conventions and distinguishes from sibling tools like obsbot_gimbal_recenter by emphasizing absolute positioning.

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 implies use for absolute moves but lacks explicit guidance on when to prefer this over alternatives like presets or recentering. No when-not or alternative comparisons are provided, though the context is clear.

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