delete_selected_items

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

The destructiveHint annotation already signals mutating behavior, and the description adds the 'all selected' scope. However, it does not disclose whether the operation is undoable, whether it no-ops with no selection, or whether it affects only media items. The description is consistent with the annotation but adds limited behavioral detail.

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, direct sentence that front-loads the action and scope. Every word earns its place, and there is no redundant or filler content.

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 no-parameter, destructive tool, the description conveys the core behavior, but it leaves gaps around what 'items' means and what happens if nothing is selected. Given the destructive nature and no output schema, slightly more context would help an agent invoke it confidently.

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 tool has zero parameters, so the input schema is complete by definition. The description does not need to explain parameter semantics, and there is no ambiguity introduced by missing parameter documentation.

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 clearly identifies the action (delete), the resource (selected items), and the scope (all). It is distinguishable from singular tools like delete_item and from selection-oriented tools like cut_selected_items, though it does not explicitly state that 'items' refers to media items rather than tracks or other entities.

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?

There is no guidance on when to use this tool instead of alternatives such as delete_item, cut_selected_items, or clear_track. The intended context (delete all currently selected media items) is only implied by the name and description, with no explicit exclusions or prerequisites.

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