delete_bin_item

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the bar is lower; the description still earns credit for adding '(undoable)', which is real context not present in annotations. However it omits high-value behavior for a destructive call: whether deleting a bin cascades to its contents, and whether underlying media files on disk are affected or only the project reference.

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 with the resource list and reversibility caveat; no padding or repeated information. Efficient for the amount of content present.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. What remains missing is the one thing an agent cannot infer: how to form a valid 'path' for an irreversible-looking delete, plus cascade behavior — a material gap for a two-parameter destructive tool with zero schema documentation.

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 description coverage is 0% and both parameters are bare strings, so the description must compensate — it does not. It says nothing about the format of 'path' (filesystem path, bin hierarchy path, or item identifier) or what 'project' does when null, which is the primary ambiguity risk for a delete operation.

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?

States a specific verb ('Remove') and enumerates the affected resource types (bin, clip, sequence), which separates it from the sibling deletion tools delete_track and delete_track_items that operate on tracks. It does not distinguish bin-vs-clip-vs-sequence handling, but the resource scope is unambiguous.

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 on when to prefer this over delete_track_items, close_project, or remove_tag, and no prerequisites or exclusions. The parenthetical '(undoable)' hints at recovery but does not tell the agent when this tool is the right choice.

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