move_bin_item

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is known; the description usefully extends this by clarifying which item kinds can be moved and that the root is a valid destination. It says nothing about what happens on name collisions in the target bin, whether the item keeps its position, or what errors occur for invalid paths.

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 scope and destination up front. The parenthetical about the project root earns its place, though its mangled empty-string literal reduces rather than improves clarity.

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 no explanation, but for a 3-parameter mutation tool with zero schema descriptions the description leaves too much open: meaning of each parameter, what a move does to the source bin, and any failure modes.

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% for 3 parameters, so the description must compensate, and it largely does not. It explains only that the empty-string destination means project root (and even that is garbled in the text as '""'), leaving 'path' (source item path? name?) and 'project' (which project, default null behavior) undefined.

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?

Specific verb ('Move') plus resource enumerated ('a bin, clip or sequence') and the destination concept ('into another bin'). It is implicitly distinguishable from siblings like rename_bin_item and delete_bin_item, but never explicitly contrasts with them.

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?

The move semantics imply when to use it (relocating an existing item to a different bin), but there is no explicit when/when-not guidance, no mention of alternatives such as create_bin + delete_bin_item, and no prerequisites (e.g., project must be open).

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