move_cell

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 key behavioral trait that existing cells shift, but does not mention potential side effects, error conditions, or whether the operation is reversible. This is adequate for a simple move but lacks depth.

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, clear sentence that is well front-loaded and contains no unnecessary words. Every part of the description earns its place.

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 simplicity of the operation (move a cell to an index) and the absence of an output schema, the description is mostly complete. It could mention that the operation reorders the cell list or specify that indices are 0-based, but overall it is sufficient for an agent to understand the core functionality.

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?

Although the input schema already describes both parameters (cellId, cellIndex), the description adds behavioral context by explaining that moving a cell shifts existing cells, which gives meaning to the index parameter beyond its type and constraints.

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 a cell') and the target ('to the provided index'), with the additional effect of shifting existing cells. This distinguishes it from siblings like add_cell, delete_cell, or update_cell, which perform different operations.

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 provides no guidance on when to use this tool versus alternatives (e.g., reordering via delete/add). It does not mention prerequisites, limitations, or exclusions, leaving the agent without contextual decision support.

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