vector_look

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only restates the core action. It does not mention side effects (e.g., whether the head moves), prerequisites (e.g., whether the camera must be enabled), or what happens after capture (returned image, saved file, etc.).

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?

A single, front-loaded sentence communicates the essential operation with no filler. Every word is useful and the structure is immediately scannable.

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 parameterless tool, the description minimally conveys what happens, but it is incomplete in context because the sibling list contains vector_capture_image, which likely overlaps in function. It also does not state the output form or any caveats, though the lack of an output schema leaves some latitude.

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 input schema has zero parameters, so there is no parameter documentation burden. The description correctly avoids inventing parameters and needs to convey no additional parameter-level semantics.

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 states a specific action ('capture an image') and a concrete resource ('the robot's front camera'), so an agent can understand the basic operation. However, it does not differentiate this tool from the sibling vector_capture_image, which appears to have the same purpose, so it falls short of full clarity.

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?

No guidance is given about when to use vector_look versus alternatives such as vector_capture_image or vector_scan. The description only states what the tool does, not when it should be chosen or what conditions apply.

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