delete_multiple_project_items

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

With no annotations, the description must carry the full behavioral disclosure burden. It only states that the tool deletes multiple project items, but does not explain permanence, undoability, selection mechanism, or any side effects. This is a significant gap for a deletion operation.

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 very brief and front-loaded with the core action. The phrase 'expanded operation' is unnecessary filler, but it does not significantly harm readability. Overall, it is concise and to the point.

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?

The operation is a deletion tool with no annotations, no output schema, and an empty input schema. The description fails to clarify how the items to delete are identified (e.g., selected items, list of IDs), and how this differs from similar tools. This lack of context makes it hard for an agent to know how to invoke it correctly.

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 is an empty object with 0 parameters, so the baseline is 4. The description does not add parameter semantics, but there are no parameters to describe, so this is acceptable.

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 states the action ('delete') and the resource ('multiple project items'), which distinguishes it from the sibling tool delete_project_item (singular). However, the phrase 'expanded operation' is vague and adds no meaningful content.

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?

No guidance is provided on when to use this tool versus alternatives like delete_project_item or remove_selected_clips. The description only implies it handles multiple items, but does not explicitly state scenarios or exclusions.

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