reachy_capture_image

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It states only that a single frame is captured; it does not mention whether the frame is saved, returned, or streamed, nor any permissions, delays, or side effects. This is a minimal behavioral statement with little transparency.

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?

The description is a single concise sentence that front-loads the action, resource, and scope ('single frame'). Every word contributes meaning and there is no redundant or boilerplate content.

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 zero-parameter tool, the description is arguably sufficient to invoke: the agent can call it with no inputs. However, because there is no output schema and no annotation context, the missing return/behavior details leave some ambiguity about what the agent should expect after the call, so it is adequate but not fully 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?

The tool has zero parameters, so the baseline is 4. The description correctly adds no parameter information because there is nothing to add; there are no input semantics to clarify.

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 verb ('Capture') with a clear resource ('a single frame from the robot's camera'). It is distinct from siblings like reachy_start_webrtc_stream, which implies continuous video, and reachy_check_camera, which implies testing rather than capturing a frame.

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 phrase 'single frame' implies use when a still image is needed, and implicitly contrasts with streaming or checking. However, no explicit guidance is provided about when to prefer this over reachy_check_camera or reachy_start_webrtc_stream, so the usage context is only implied.

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