remove-from-album

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

With no annotations, the description fully carries the behavioral disclosure burden. It covers write-enablement (APPLE_PHOTOS_MCP_ENABLE_WRITES=1), the rebuild behavior with UUID change and sort order loss, scratch album naming, interruption safety, max 100 UUIDs, and AppleScript permissions—far beyond what annotations would provide.

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 dense but front-loaded with the key 'Use when' guidance. Every sentence adds critical operational detail; however, it runs long and could be tightened without losing essential information.

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 description covers return values (album after operation, removedCount, removed, notInAlbum, albumRecreated, previousAlbumUuid), failure modes (interrupted rebuild, stranded temp album), and library context (cannot delete photos). This is complete for a complex write tool with no annotations and a rich output schema.

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 100%, so the baseline is 3. The description adds meaningful semantics beyond the schema: album accepts name or UUID with the UUID-looking-first resolution order, and the response semantics (notInAlbum, albumRecreated) clarify edge cases. This pushes it a point above baseline.

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 uses a specific verb (remove) with a clear resource (album membership) and explicitly contrasts with deletion ('Do not use when: you want to delete photos from the library'). It also distinguishes from siblings like add-to-album and set-photo-metadata by stating 'removes ALBUM MEMBERSHIP only'.

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 gives explicit 'Use when' and 'Do not use when' conditions, including a concrete alternative (quarantine in an album and review in Photos.app). This directly addresses tool selection vs. alternatives and clarifies when the tool is inappropriate (photos not in album).

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