photos_import_file

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

With no annotations, the description carries full burden. It discloses the multi-step sequence, dependency issues (stage=afc in ≤5s), video constraints (avoid parallel sessions, expect needsRetry), and optional verify. Lacks explicit success/failure return format, but covers key behavioral traits.

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?

Two dense sentences with front-loaded '[advanced]' and key info. The structure is somewhat run-on but packs relevant details. Could be split for readability, but every word earns its place.

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 4 params, no output schema, and no annotations, the description covers dependencies, fallback, and constraints. However, it does not explain what the tool returns (e.g., localIdentifier or error), leaving a gap for an agent to infer 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 coverage is 50% (udid lacks description). The description repeats 'Accepts image or small mp4' (matching mediaType enum) and mentions 'verify' default true, but adds little beyond schema. Does not explain udid or provide format details for localPath. Baseline 3 since schema covers half.

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 it performs a multi-step import (AFC upload, Photos ensure, PhotoKit import, optional verify) for images or small MP4s. It distinguishes itself from siblings like 'photos_import' by labeling itself as 'advanced' and 'preferred for AI', though the jargon may not be universally clear.

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?

Provides context on when to use ('preferred for AI'), dependency requirements, fallback behavior on missing deps, and a warning against parallel session_open for video. It does not explicitly contrast with sibling tools like 'photos_import' or 'photos_ensure', but the guidance is actionable.

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