import_from_camera

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

With no annotations provided, the description carries the full burden, and it does so thoroughly: it explains libgphoto2 detection, non-overwriting collision behavior, filename/subdirectory conventions, serial-number edge cases, timeout/resume semantics, and observable progress via .import.log. These are genuine behavioral disclosures beyond what a schema could infer.

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 long but information-dense, with the primary use condition front-loaded and every sentence serving a distinct purpose. Slight structural awkwardness in the later edge-case sentences and an embedded user directive ('Import the destination recursively.') keep it from a perfect score.

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 tool with no output schema and meaningful side effects, the description is remarkably complete: it states the return value, the follow-up workflow, collision handling, timeout behavior, progress observability, and naming rationale. An agent has enough context to invoke it correctly and debug its behavior.

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 100%, so all three parameters are already documented in the input schema. The description adds some operational context around destination subdirectories and timeout recovery, but it does not materially extend parameter meaning beyond what the schema already provides.

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 names a specific action ('copies all photos to a local directory'), identifies the physical-camera context, and explicitly separates this from the library-registration step performed by import_batch. The tool's scope is unambiguous and clearly distinguished from its siblings.

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?

It opens with the exact condition for use ('Use when a camera or memory card is physically connected') and explicitly instructs to follow up with import_batch on the returned destination path. This provides both when-to-use and when-not-to-stop guidance, with the alternative tool named directly.

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