photos_import

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

Discloses that the tool imports a file and returns a localIdentifier, and mentions the terminateAfter parameter's effect (killing Photos). However, it omits behavior when paths are invalid, mediaType mismatches, or import fails. No annotations to rely on.

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 a single sentence that packs essential information: purpose, path constraints, host limitation, and return value. It is concise without being overly brief, though it could be slightly more structured.

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 5-parameter tool with no output schema and no annotations, the description covers the core mechanism but leaves gaps: no explanation of udid, no error behavior, and no differentiation from the sibling photos_import_file. The return value is mentioned but not the structure.

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?

With 60% schema description coverage, the description adds minimal value beyond the schema. It reiterates path locations but does not clarify the udid parameter, the role of mediaType, or the distinction between devicePath and remotePath. The terminateAfter context is helpful but insufficient to compensate.

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?

Clearly states it imports already-on-device files from specific paths under /DCIM into Photos. The '[advanced]' and 'Host=Photos.app only' qualifiers add precision, but it does not explicitly distinguish from sibling 'photos_import_file' which might have a different scope.

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?

Specifies that file must be on device under /DCIM and that it targets Photos.app, but provides no guidance on when to use this tool versus alternatives like photos_import_file, nor any prerequisites or error handling scenarios.

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