delete_bin

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

No annotations are provided, so the description carries full burden. It only says 'expanded operation' and 'delete bin' without disclosing dangers like permanent deletion, cascade effects on clips/sequences, or confirmation requirements. Lack of safety warnings is a serious gap.

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 short (one phrase) and provides no structured information. It is under-specified, not concise; it omits critical context and reads like a placeholder.

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?

Given the deletion operation and absence of annotations/output schema, the description is inadequate. It does not explain return values, error handling, or behavior on non-empty bins. The tool name 'delete_bin' and the note 'Premiere Pro expanded operation' add nothing actionable.

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?

Parameter count is 0, so the schema provides no parameter info. The description adds no param semantics, but with zero parameters the baseline is 4. However, it offers no explanation of how the tool identifies which bin to delete (e.g., requires a selected bin), which could be considered lacking.

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 says 'delete bin' but gives no detail on scope (deletes from disk or project?), effect on contained items, or whether it is a permanent action. It merely restates the tool name with action verb, offering minimal differentiation from siblings like 'delete_project_item' or 'delete_sequence'.

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 use this tool versus alternatives like 'delete_project_item' or 'move_items_to_bin'. The description implies it deletes a bin, but does not specify prerequisites, effects on contents, or whether it is reversible.

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