move_card

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

With no annotations, the description carries full burden. It explains the move operation and references the column ID format, but does not disclose side effects, permissions, or handling of errors (e.g., invalid board). The default position is implied via schema but not in description.

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 two sentences with no unnecessary words. First sentence states the core purpose, second provides a critical parameter hint. Efficient and front-loaded.

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 4-parameter tool with no output schema, the description covers the main functionality and key parameter. It lacks details about return values or error conditions, but is sufficiently complete for an agent to understand the primary operation.

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 100%, so the schema already documents all parameters. The description adds marginal value by clarifying that newColumnId is a label-style string from list_columns, but does not elaborate on newBoardId or newPosition beyond what the schema says.

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 a card to a different column on the same board or another board. It specifies the action (move), the resource (card), and the scope (same or different board), distinguishing it from siblings like 'update_card' which modifies card properties.

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 implies usage by describing the action, but does not explicitly state when to use this tool versus alternatives. It provides a tip about newColumnId coming from list_columns, but lacks exclusions or comparisons to other move-related tools.

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