delete_project_item

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 only states the action, omitting critical details such as whether the deletion is permanent, requires user confirmation, removes from disk or just the project panel, or what happens if the item is in use. No safety or side-effect information is provided.

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 extremely brief, but it suffers from under-specification rather than conciseness. It omits essential details about selection context and behavior, making it too sparse to be considered well-structured. A complete description would include these details while remaining compact.

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 operation with no annotations and no output schema, the description is incomplete. It does not explain return values, success/failure conditions, prerequisite states, or the operational scope. It is not sufficient for an agent to confidently invoke the tool in a real workflow.

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, and the schema is empty. A baseline of 4 might apply, but the description fails to clarify how the target project item is identified (e.g., current selection). Without this, the agent cannot reliably know which item will be deleted, making the description insufficiently informative.

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 project item.' It clearly states the core action, and the singular 'item' implies it operates on one item, distinguishing it from the sibling 'delete_multiple_project_items.' However, it does not explicitly define the item scope (e.g., selected item), so it falls short of a 5.

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 versus alternatives like delete_multiple_project_items, remove_selected_clips, or delete_bin. The description does not mention prerequisites or context, leaving the agent without decision-support information.

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