images

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

With no annotations, the description must disclose behavior; it does add that listing includes offscreen photos, create_candidate clones the selected variant, edits are restricted to registered copies, and macOS has restrictions. However it omits side effects and permissions for select, prepare_adjustments, and prepare_tool and does not clarify mutation safety.

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 compact and front-loads the main list/select idea, but it is a dense set of jargon-laden sentences rather than an action-oriented structure. Terms like native collection, offscreen photos, registered copies, and collection_token are not defined.

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 an 11-parameter, seven-action tool with no annotations and no schema descriptions, this description is far from complete. It offers useful hints for a few paths but leaves most of the action surface undocumented; the output schema only removes the need to explain return values.

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 0% across 11 parameters, so the description must compensate. It only touches variant_uuid and collection_token (plus output next_offset), leaving action, scope, limit, offset, target, request_id, variant_id, observation_token, and tool enum values unexplained.

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 first sentence names list and select on a native collection, but the tool exposes seven actions (prepare_adjustments, prepare_tool, next, previous, etc.) and the generic name 'images' does not establish the overall purpose. It is not clear how this differs from siblings such as read or preview.

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 gives action-specific operational guidance (same collection_token for pagination, next/previous on filtered collection, create_candidate behavior, macOS-only listing/selection) and points to context for platform restrictions. It does not say when to choose this tool instead of siblings or explain the prepare_* actions.

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