zuuna_move_card

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

With no annotations, the description carries the behavioral burden. It transparently states the mutation ('move a card') and adds useful detail about column title resolution being board-scoped and accepted card identifiers. However, it does not mention return values, failure behavior, or whether this is reversible.

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 concise sentences with no redundant phrasing. The primary action is front-loaded, followed immediately by the key disambiguation details for card and column identification.

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 move operation with only three parameters, the description is mostly sufficient. The main gaps are the absence of any indication of what the tool returns (there is no output schema) and no mention of error conditions or prerequisites, which an agent might need to handle failures gracefully.

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%, so the schema already documents all three parameters. The description repeats this information without adding new semantic detail beyond clarifying that columnTitle is resolved against the card's board—which the schema also states. Baseline 3 is appropriate.

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 a card to another column') and the resources involved (card, column, board). It distinguishes itself from sibling tools like zuuna_create_card and zuuna_update_card by naming a unique 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?

The description provides clear context for when to use the tool: whenever a card needs to be moved to another column. It also explains how to specify the destination via columnId or columnTitle, though it does not explicitly discuss exclusions or compare against sibling tools.

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