move_item_to_bin

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

No annotations are present, so the description carries the full burden of behavior disclosure. It merely restates the name, omitting critical details: whether the move is a rename/refile or physical relocation, what happens to sub-items or metadata, error handling, and side effects. This is a significant gap for a mutation tool.

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 sentence with no redundant information. While concise, it could be more informative without sacrificing brevity.

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 absence of annotations, output schema, and nested objects, the description should provide more context about the operation's effects, return value, and constraints. It fails to cover common questions like 'what happens if item already in target bin?' or 'does this work across bins in different folders?'.

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 coverage is 100%, and parameter descriptions already define the expected input semantics (node ID or name). The description adds no additional meaning, so the baseline score is appropriate.

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 (move) and the objects (project item to different bin). It is specific enough to distinguish from basic move operations, but there is a sibling tool 'move_items_to_bin' which handles multiple items, and the singular/plural distinction is not clarified, leading to potential ambiguity.

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 alternatives like 'move_items_to_bin', 'move_clip', or 'move_clip_to_track'. There are no conditions, prerequisites, or exclusions mentioned, leaving the agent without decision context.

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