photos_remove_from_album

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

The description adds important context beyond the destructiveHint annotation by clarifying that the destructive scope is limited to album membership, not library deletion. It also discloses the authentication requirement, which is valuable behavioral info.

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 three concise sentences, each adding value: purpose, authentication, and path constraints with behavioral effect. No redundant words.

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 simple two-parameter tool with no output schema, the description covers purpose, behavioral impact, prerequisites, and path constraints. It is complete enough for an agent to confidently select and invoke the tool.

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?

The input schema already provides full parameter descriptions, including path format constraints and examples. The tool description reinforces the path prefix requirements but does not add new semantic information beyond what the schema 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 states a specific verb and resource: 'Remove a photo from a Proton Photos album' and clearly clarifies the scope by saying 'without deleting it from your library.' This differentiates it from sibling tools like photos_add_to_album and photos_delete_album.

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 clear context for when to use this tool (removing from an album while keeping the photo) and mentions the authentication requirement. However, it does not explicitly name alternative tools or state when not to use it, though the context implies the distinction.

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