look

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

With no annotations, the description carries the full burden and does real work: 'observes' establishes it is non-mutating, and it discloses output limitations ('a still only tells you what is in front of the lens -- not where the camera is, and not whether a move happened'). It omits anything about permissions, latency, or failure modes, but the interpretive caveat is genuinely useful.

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 core action and output format are front-loaded in the first sentence, followed by usage and limitation notes. It is efficient overall, though the second sentence runs long and the caveat clause is slightly more verbose than needed.

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 and no annotations, the description supplies what a caller needs: what is returned (a PNG frame of the current view) and what that frame cannot tell the agent. Nothing critical about invocation is missing, though return-handling details (e.g., where the image lands) are left implicit.

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 takes zero parameters, so the baseline is 4. The description correctly implies no inputs are needed to trigger a capture, and there is nothing for it to disambiguate.

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: 'Capture one frame of what the camera currently sees, as a PNG image.' It is unambiguous against siblings like go_to or sweep, though it never names which sibling to use instead for related tasks (e.g., check_view), so it stops short of explicit sibling 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?

Gives an explicit trigger ('Call it when the user asks to see the picture') and an explicit exclusion ('not on your own initiative'). That is strong when/when-not guidance, but it does not point to any alternative tool for cases the agent might confuse with this one.

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