list_move_to_board

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

No annotations, so the description carries the full burden. It does disclose one important side effect — the move changes who can access the list and its cards — which is genuinely beyond structured data. However it says nothing about required permissions (e.g., admin on both boards), reversibility, or what happens to list position on the destination board.

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?

Two short sentences, zero filler, with the core action and its access-permission consequence front-loaded and the alternative tool named second.

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 two-parameter mutation with no output schema and no annotations, the definition covers purpose, side effect, and the nearest alternative. Missing authorization requirements and failure behavior keep it from being fully complete.

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%, with both listId and boardId fully documented in the schema, so the baseline of 3 applies. The description confirms the semantic role of each (source list, destination board) but adds no format or constraint detail beyond that.

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 (an existing list and its cards) with the destination scope (another board). It also flags the non-obvious consequence — access permissions change — which distinguishes it from a plain reorder operation.

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?

Explicitly routes the agent: use list_update to reorder within the current board, this tool for cross-board moves. It doesn't contrast with card_move (single-card moves) or state prerequisites, but the primary ambiguity is resolved.

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