move_cell

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

The description discloses the index positions and their 0-based nature, but with no annotations, it fails to reveal side effects (e.g., reindexing of other cells), permissions required, or if the move is reversible. It provides basic behavioral context but lacks comprehensive transparency.

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, well-structured sentence that efficiently conveys the tool's purpose and key parameter behavior. Every word is informative, and the description is front-loaded with the action and resource.

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 and output schema, the description is insufficient. It does not explain the 'path' parameter, the return value (if any), or how the move affects other cells. More context is needed for complete understanding.

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 meaning for 'from_index' and 'to_index' by explaining their role as source and target positions. However, the 'path' parameter is completely unexplained, and the schema provides only type/title. With 0% schema coverage, the description only partially compensates for the missing parameter semantics.

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), the resource (cell), and the key parameters (from_index, to_index). It specifies the behavior (final position, 0-based), making it distinct from sibling tools like delete_cell or insert_cell.

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. It does not mention prerequisites, typical use cases, or situations where this tool is preferred over other cell operations.

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