move_card

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It states that the tool 'Returns the updated card', but does not mention side effects, permissions, reversibility, or constraints. The description is minimal and leaves significant gaps.

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 extremely concise: two sentences plus a structured Args/Returns section. Every sentence adds value, and the main action is front-loaded. No unnecessary words or repetition.

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?

For a simple tool with two required parameters and no output schema, the description covers the purpose, parameter explanations with examples, and the return value. However, it lacks information about error conditions, such as invalid card_ref or cell_id, which could be important for reliability.

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 description coverage is 0%, but the description adds value by providing an example for card_ref ('ON-914') and explaining that cell_id is the target cell ID, along with a hint to use get_board_cells. This goes beyond the raw schema, though more detail on constraints (e.g., valid cell IDs) would improve it.

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 verb 'Move' and the resource 'card to a different column (cell) on the board'. This effectively distinguishes it from sibling tools like archive_card or assign_card, which have different purposes.

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 helpful context by directing users to use get_board_cells() to find cell IDs, which aids correct invocation. However, it lacks explicit guidance on when not to use this tool or how it compares to other move-related tools like move_card_to_iteration.

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