delete_items_in_range

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

With no annotations, the description carries the full burden and discharges most of it: it flags the operation as destructive, notes it is undo-block wrapped, and that it supports dry_run for safe preview. It does not describe return format or what happens to surrounding content, but the key safety behaviors are surfaced.

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?

A single front-loaded sentence leads with the verb and resource, then adds the three most decision-relevant caveats (destructive, undo-block, dry_run) with zero filler.

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 9-parameter destructive tool with no output schema and no annotations, the description supplies the critical safety context an agent needs. It stops short of clarifying the nested position-object options or default behavior, but those are covered by the schema.

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 coverage is 67% and the schema itself documents range, track, dry_run, track_contains, target_track_guid, and use_selected_track in detail. The description only echoes the all_tracks and dry_run options and adds no syntax or format guidance beyond the schema, so it is at the baseline.

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 a specific verb (Delete), resource (media items), and scope (in a time range on one track or all_tracks). An agent can immediately tell what the tool does and its targeting breadth without opening the schema.

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?

It advises confirming intent and notes dry_run support, which implies a preview-then-execute workflow, but it never states when to prefer this tool over sibling mutation tools like raw_command or batch. Usage is implied rather than explicitly framed.

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