Move a card to another list

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

Annotations already indicate a mutation that is not destructive. The description adds the same-board constraint and position default, which are useful, but it doesn't disclose additional side effects or permission requirements. Given annotation coverage, this is minimally adequate.

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?

Three concise sentences deliver purpose, parameter sourcing, and optionality without extraneous words. The most important information is 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?

For a simple move operation with only three parameters and no nested objects, the description covers the core mechanics. It doesn't mention return behavior, but that's likely not critical for invocation; still, a bit more context on what happens after the move would enhance completeness.

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 schema describes all parameters at 100%, but the description enhances list_id by pointing to get_lists and clarifies the default value of position. This adds practical meaning beyond the schema.

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 list on the same board, using a specific verb and resource. It distinguishes from siblings like archive_card or update_card by focusing on relocation between lists.

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?

It provides context by noting list_id comes from get_lists and position is optional, but it doesn't explicitly state when to choose this over update_card or other alternatives. No exclusionary guidance is given.

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