camera_capture

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

No annotations are provided, so the description carries the full burden. It discloses that a file is saved and the full path is returned, and explains the autofocus parameter behavior. However, it does not mention potential side effects like file overwriting, required permissions, or camera state changes.

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 two short sentences, front-loaded with the core purpose and output. Every word earns its place—no fluff or repetition.

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 is simple with one optional parameter and an output schema. The description covers purpose, output, and parameter semantics. It is adequate for the tool's complexity, though it omits minor details like file naming conventions or storage location, which are not critical for invocation.

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 schema has no descriptions (0% coverage), but the description adds meaningful detail: autofocus=False enables fixed-focus shooting, implying autofocus=True is the default. This fully clarifies the only parameter, which is helpful for the agent.

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: take one shot and return the full path of the saved file. It uses a specific verb (capture) and resource (camera/file), and the output is explicit. This distinguishes it from sibling tools like timelapse_start or video_create.

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 description implies usage for single-shot capture, but does not explicitly mention when to use it over alternatives. The sibling names give context, but the description itself lacks 'when to use' or 'instead of' guidance.

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