pan_tilt_overview

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

No annotations are present, so the description carries the burden. It discloses the crucial async behavior ('Returns immediately; the sweep takes a while'), which is a genuinely helpful behavioral trait. However, it doesn't disclose what happens if called during an existing movement, whether it can be interrupted by pan_tilt_stop, or any completion indication (e.g., via camera_status).

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?

Extremely compact: two short sentences. The first sentence states the action, the second clarifies the async return. No filler. This is an example of appropriately sized, front-loaded description.

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?

The tool has zero parameters and an output schema exists, so description needn't explain return values. The only notable gap is lack of guidance on interaction with siblings (e.g., can pan_tilt_stop cancel this sweep?). Without annotations, some operational context is missing, but for a zero-param async command, this is otherwise 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?

There are zero parameters, so no param semantics are needed. Baseline for 0 params is 4; the description's mention of a 360-degree sweep serves as the only required semantic context. No parameter documentation issues exist.

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 uses a specific imperative verb ('Start'), names the exact resource ('full 360 degree pan overview'), and clearly contrasts with the 'returns immediately' behavior. This distinguishes it from siblings like pan_tilt, pan_tilt_nudge, and pan_tilt_stop.

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?

Implies when to use it (when a full sweep is desired), but provides no explicit guidance on when not to use it, prerequisites (e.g., camera on/off, calibration), or whether it conflicts with other movements like pan_tilt or pan_tilt_nudge. With no annotations, more explicit usage guidance would be expected.

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