item_move

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

With no annotations, the description carries the full burden. It discloses the basic behavior (move item to new position) but omits potential side effects like shifting other items or validation of indices. It does not contradict any hypothetical annotations.

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 highly concise with two succinct lines for arguments. It front-loads the purpose and avoids verbosity, though it could slightly expand without being wasteful.

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 no output schema and the tool's state-modifying nature, the description lacks information on return values, error cases (e.g., invalid index or position), or interactions with other items. This is insufficient for reliable use.

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 description adds minimal value beyond the schema: it clarifies that new_position is in seconds. However, item_index is only described as 'Item index' which is vague, and schema coverage is 0%, so more could be added.

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 tool moves an item to a new position, and the verb 'Move' combined with 'item' and 'new_position' makes the purpose distinct from sibling tools like item_move_to_track or item_set_length.

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 such as item_move_to_track (for moving between tracks) or item_set_length (for adjusting duration). The description lacks context for conditional usage.

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