Delete photo album

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

Annotations only say destructiveHint=true; the description adds genuinely non-obvious behavior: refusal on non-empty albums, the force override, the guarantee that underlying photos are preserved, and the confirmed gate. It also discloses the save parameter's lack of observable effect, which is exactly the kind of quirk an agent cannot infer elsewhere.

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?

Front-loaded with the verb and resource, then layers prerequisites, side effects, and the save caveat in five tight sentences with no filler. Each clause carries decision-relevant 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?

For a destructive tool with destructiveHint already declared and no output schema, the description covers prerequisites, failure modes, side effects, and safe-invocation workflow. Nothing an agent needs to call this correctly is missing.

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 description coverage is 100%, so the baseline is 3, but the description adds real semantic value on top: confirmed is framed as user acknowledgement, force as the non-empty-album override, and save is actively advised against ('leave it off unless asked'). This is more than the schema restates.

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?

States a specific verb and resource ('Delete a Proton Photos album') and immediately scopes the blast radius ('Never deletes your own photos; they stay in the timeline'), which distinguishes it from sibling tools like photos_remove_from_album and photos_update_album. An agent knows exactly what object is destroyed.

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?

Gives clear preconditions (confirmed=true), the force condition for non-empty albums, and a workflow instruction ('Show the user the album name and photo count first'). It does not explicitly name an alternative tool for the case where the user wants to remove the photos rather than the album, so it stops short of full routing guidance.

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