move_all_cards

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

No annotations are provided, so the description must carry the full burden. It only states the action without disclosing side effects, permission requirements, reversibility, or potential impacts of bulk-moving many cards. For a mutation tool, this is a significant gap.

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 short and front-loaded, but the second sentence ('Use this tool to quickly move all cards from one list to another.') is largely redundant with the first, adding only the adverb 'quickly'. This wastes a sentence without adding new information.

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 bulk operation with no output schema and no annotations, the description is too minimal. It does not explain return values, potential performance considerations, or the broader context of moving all cards (e.g., whether the source list becomes empty or if there are limits). This is inadequate for an agent to fully assess the tool's effects.

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 baseline is 3. The description adds no extra meaning beyond the schema, which already explains sourceListId, destinationListId, and boardId. The optional fields/detailLevel parameters are not mentioned but are already described in 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 action ('Move all cards in a list to another list') with specific verb and resource. It distinguishes itself from the sibling tool 'move_card_to_list' by explicitly targeting all cards, making the scope unambiguous.

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 ('Use this tool to quickly move all cards from one list to another'). However, it does not explicitly mention alternatives or exclusion criteria, such as using 'move_card_to_list' for individual card moves.

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