gallery_delete_stills

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

The destructiveHint annotation already flags this as destructive, so the description doesn't need to do so. It adds that deletion is by index, which indicates a precise removal rather than bulk, but doesn't disclose whether the action is irreversible or any additional side effects. This is acceptable given 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?

One sentence, immediately states verb and object. No extraneous 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?

With a high-coverage schema, a destructiveHint annotation, and an output schema present, the description is sufficient for the agent to understand the operation. The only context (indices from gallery_get_stills) is captured in the parameter description.

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 covers 100% of parameter descriptions, including zero-based indices and album_name defaulting. The description itself adds no parameter details beyond the schema, so a baseline 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 states exactly what the tool does: deletes stills from a Gallery album using index-based targeting. This clearly distinguishes it from sibling tools like gallery_delete_album (deletes an album) and gallery_get_stills (retrieves stills).

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 implies that still indices should be obtained from gallery_get_stills, and the schema further clarifies that album_name defaults to the current album. However, it does not explicitly state when to use this tool versus alternatives or provide exclusion criteria, so it stops short of a 5.

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