look_and_analyze

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. It mentions movement and analysis, but lacks details on permissions, rate limits, whether the analysis is real-time or delayed, what happens if parameters are out of range, or if the camera movement is blocking. This leaves significant gaps for a tool with physical and analytical effects.

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 extremely concise with a single, front-loaded sentence that captures the core functionality without any wasted words. It efficiently communicates the tool's purpose in a minimal format, making it easy to parse quickly.

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?

Given the complexity (physical camera control with analysis), lack of annotations, 0% schema coverage, and no output schema, the description is incomplete. It doesn't address key aspects like what the analysis returns, error conditions, or practical usage constraints, leaving the agent with insufficient information to use the tool effectively in real scenarios.

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 description coverage is 0%, so the description must compensate for all parameter documentation. It does not explain what 'pan', 'tilt', 'zoom', or 'analysisPrompt' mean, their units, or how they interact. For example, it's unclear if 'pan' and 'tilt' are in degrees or steps, what 'zoom' levels correspond to, or what the 'analysisPrompt' influences. This fails to add meaningful context beyond the bare schema.

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 camera to position and take analyzed snapshot'), specifying both physical movement and analytical capture. It distinguishes from siblings like 'center_camera' (only movement) and 'take_snapshot' (only capture without analysis), though it could be more explicit about the 'analyzed' aspect versus raw capture.

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 explicit guidance on when to use this tool versus alternatives is provided. The description implies it combines camera positioning with analytical snapshot capture, but it doesn't specify scenarios where this is preferred over using separate tools like 'control_gimbal' followed by 'take_snapshot', or when to choose 'scan_area' instead for broader analysis.

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