gallery_delete_album

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

Annotations already provide destructiveHint: true, so the destructive nature is covered. The description adds the context that it's specifically a 'still album' but does not disclose additional behavioral details such as whether contained stills are deleted or if the operation is permanent. With annotations in place, this is adequate but not enriched.

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 a single, complete sentence that is immediately understandable and front-loaded with the action and object. No filler or redundant 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 simple one-parameter destructive operation with an output schema and a clear annotation, the description is largely sufficient. It could have mentioned side effects like deletion of contained stills, but the combination of schema and annotations covers the essential context.

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 single parameter album_name is fully described in the schema ('Name of the album to delete'), and the description adds no extra semantic value. With schema description coverage at 100%, the baseline of 3 is appropriate.

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 ('Delete') and resource ('a still album from the Gallery'), clearly distinguishing it from sibling tools like gallery_delete_stills (which deletes stills, not albums) and gallery_create_album (which creates). The phrase 'still album' also differentiates from powergrade albums.

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 clearly implies when to use it (when you need to delete a still album), and the resource type naturally distinguishes it from gallery_delete_stills and gallery_get_albums. However, it does not explicitly state alternatives or exclusions, so it stops short of a perfect score.

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