aim

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 richly: latency expectations (about one second for gimbal, three for zoom), value clamping to the camera's advertised range, synchronous waiting, and the crucial disclosure that success is decided by frame comparison rather than the device's unreliable self-report.

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-loaded with the core action, then layered with units, timing, and verification semantics. Dense but each sentence carries distinct operational value; the parenthetical about clamping is well placed. Slightly heavy for a two-parameter tool, but nothing is filler.

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?

With no output schema, the description usefully names the return signals (`moved` from frame comparison, `device_reported` as an untrusted hint) and spells out the failure condition when the picture shows no change. A brief note on the full response shape or the `axis` value constraints at the schema level would make it complete.

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% and the schema is bare (`to`, `axis` with no descriptions or enums), so the description must compensate fully — and it does. It enumerates the axis domain (pan, tilt, roll, zoom), gives units (degrees; zoom as ratio x100, so 300 = 3x), and explains that `to` is clamped to the camera's advertised range.

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 ("Point one axis at an absolute value") and tightens the scope with the axis domain and units. The phrase "one axis" and "absolute value" implicitly separates it from relative siblings like `nudge`, but no sibling is named explicitly, so it stops short of full differentiation.

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?

Usage is implied rather than stated: the agent can infer this is for absolute one-axis moves, and the mention that zoom is handled via axis=zoom partially disambiguates from the `zoom` sibling. However, there is no explicit when-to-use vs `nudge`, `recentre`, `go_to`, or `zoom` guidance and no stated prerequisites.

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