move_item_to_bin

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

No annotations are provided, so the description carries the behavioral burden. It conveys the core behavior: the item is moved, not copied, into a different bin. However, it does not disclose additional behavioral details such as whether the item is removed from its original bin, whether the target bin must exist, or how errors are handled.

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 sentence with no filler. It front-loads the verb and clearly identifies the action and destination, making it easy to parse quickly.

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 simple two-parameter move operation with no output schema, the description is minimally adequate. However, the lack of any usage differentiation from move_items_to_bin and the absence of side-effect or precondition details leave the context only partially complete.

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 has 100% description coverage for both required parameters, so the baseline applies. The description adds no parameter-level detail beyond using the general terms 'project item' and 'bin,' which loosely match projectItemId and targetBinId but do not extend the schema's documentation.

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 ('Moves'), the resource ('project item'), and the destination ('bin (folder)'). It distinguishes the tool from timeline-related operations like move_clip_to_track, but it does not explicitly contrast it with the near-sibling move_items_to_bin, so it is clear but not fully differentiated.

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 about when to use this tool instead of alternatives. In particular, the sibling tool move_items_to_bin exists, and the description does not clarify singular versus bulk moving, nor does it mention any preconditions such as the target bin already existing.

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