delete_multiple_project_items

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

With no annotations, the description carries the full burden of behavioral disclosure. It indicates a destructive action, but does not say whether the deletion is permanent, whether it can be undone, whether it requires a selection, or what constraints apply. The absence of these details is significant for a mutating tool.

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, short sentence and is easy to scan. However, the 'Premiere Pro expanded operation:' prefix is not clearly valuable and uses words without adding concrete meaning. Overall it is concise, but not every word earns its place.

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 annotations, no output schema, and no parameters, the description is too sparse. It never explains how the target items are determined, what the preconditions are, or what happens after deletion. An agent cannot reliably decide when to call this tool or what state it depends on.

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 input schema declares zero parameters, so there is no parameter documentation burden on the description. The schema's additionalProperties: true is unusual, but with no defined parameters the description does not need to provide parameter-level meaning. A score of 4 reflects the zero-parameter 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 uses a specific verb and resource: 'delete multiple project items'. It distinguishes the operation from sibling tools like delete_bin and delete_sequence by naming project items, though it does not explicitly contrast with those alternatives. The phrase 'Premiere Pro expanded operation' adds little and could confuse, but the core purpose is clear.

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 about when to use this tool versus alternatives such as delete_bin, delete_sequence, remove_selected_clips, or delete_marker. The description does not state whether this operates on selected project items, a supplied list, or some other context. An agent is left to infer usage entirely from the name.

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