delete_bin

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not state whether deleting a bin also deletes its contents, whether the operation is reversible (e.g., undoable), whether confirmation is required, or what side effects occur. The description is silent on all behavioral aspects, which is especially risky for a destructive 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 a single short phrase that provides no structured information. While it is concise, it is under-specified to the point of being unhelpful. It does not front-load any useful detail and fails to earn its place as a meaningful description.

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 and no output schema, the description is severely incomplete. It omits critical context such as what a bin is, how deletion behaves, what input is required, and whether the action is safe or reversible. An agent cannot confidently invoke this tool based on the current description alone.

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 essentially empty but allows additional properties. The description does not explain what parameters are expected (e.g., bin name or ID), how to specify the target bin, or any constraints. With no parameter documentation and a permissive schema, the agent has no idea what to pass. The baseline of 4 for zero parameters is not applicable because the schema leaves room for arbitrary input but the description offers no guidance.

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 'Premiere Pro expanded operation: delete bin' essentially restates the tool name without adding detail. It lacks specificity about what a 'bin' is in this context, what the deletion entails, or how it differs from sibling tools like 'delete_multiple_project_items' or 'move_item_to_bin'. It conveys only the surface action, not the precise scope or target.

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 other deletion-related tools. There is no mention of prerequisites, such as whether a bin must be selected or named, or when an alternative like 'move_item_to_bin' or 'delete_multiple_project_items' would be preferred. The agent is left with no decision support.

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