move_project_item

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

No annotations are provided, so the description carries the full behavioral burden, yet it only implies mutation via the verb 'move'. It does not state whether the target bin must exist or is auto-created, whether the move is reversible, what happens on a missing nodeId, or what the call returns. For an unannotated mutation tool this is a significant 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?

A single short sentence with the action front-loaded and zero filler. It is efficient, though the brevity is partly under-specification rather than disciplined conciseness.

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?

The tool is structurally simple (2 required params, full schema coverage, no nesting), but with no annotations and no output schema the description should at minimum cover preconditions and return behavior. Neither is addressed, leaving an agent unable to predict failure modes when moving into a nonexistent or nested bin path.

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%, so both parameters are already documented in the schema, which sets the baseline at 3. The phrase 'to a different bin' slightly reinforces that targetBinPath is a bin path rather than an arbitrary identifier, but adds no format, path syntax, or root-level semantics beyond the schema.

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?

States a specific verb ('Move') and resource ('a project item') plus the destination ('a different bin'), which is enough to distinguish it from timeline-oriented siblings such as move_clip_to_track. It stops short of explicitly naming a sibling or clarifying the project-item vs. clip distinction, which is the main ambiguity in this catalog.

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 description gives no when-to-use context, no prerequisites, and no alternatives. An agent cannot tell from this text whether the target bin must already exist or how this differs from rename_project_item or set_project_item_label.

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