photos_delete_album

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

Beyond the destructiveHint annotation, the description discloses crucial behaviors: default refusal for albums containing photos, force override, default photo removal from album with timeline retention, and the save preservation option. This is rich context that substantially exceeds the annotation.

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 yet information-dense. Each sentence addresses a distinct aspect (function, auth/confirmation, force, save, path constraint, user confirmation step). No fluff or repetition; structure is logical and front-loaded with the primary action.

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 no output schema, the description is remarkably complete: it covers prerequisites, safety guards, behavioral nuances, parameter constraints, and a pre-call user confirmation step. It fully prepares an agent to invoke the tool correctly.

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 schema already provides 100% coverage of parameter descriptions, but the description adds meaningful context: 'albumPath must start with /albums/' and clarifies force/save default behaviors (e.g., save=true overrides default removal). This adds value beyond the schema.

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 opens with 'Delete a Proton Photos album,' a specific verb+resource that clearly states the tool's function. It distinguishes itself from siblings like photos_add_to_album and photos_remove_from_album by targeting album deletion, not photo manipulation.

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 provides explicit usage conditions: requires authentication and confirmed=true, force=true to override default refusal for non-empty albums, and save=true to preserve photos. It also instructs to show the user album name and photo count from photos_list_albums before calling, and specifies albumPath format, offering clear when-to-use and prerequisites.

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