move_card

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

No annotations exist, so the description must bear full responsibility for behavioral disclosure. It only states the basic action but omits side effects (e.g., triggers automations, column dependencies) or permission requirements, which are critical for a write operation.

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 sentence conveys the core function without excess words. It is front-loaded with the verb and resource, making it efficient for quick comprehension.

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?

Despite having three parameters (one optional) and an output schema, the description fails to explain the board parameter's role, error handling, or return value behavior. This leaves gaps in understanding, especially for an AI agent needing full context.

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 input schema has 100% description coverage, explaining each parameter's purpose. The description adds no new semantic value beyond the schema, so it meets the baseline for a schema-rich tool without further elaboration.

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 'Move a card to a different column' clearly specifies the action (move) and the resource (card) with a precise destination (different column). It distinguishes this tool from siblings like 'create_card' or 'delete_card' by focusing solely on relocation.

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?

No guidance is provided on when to use this tool versus alternatives like drag-and-drop in UI or batch moves. It lacks context about prerequisites or suitable scenarios, leaving the agent without decision support.

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