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

The description adds real value beyond annotations by disclosing scope: only open cards are copied (implying archived cards are excluded) and it explicitly names the copied fields. It also states placement (end of the same board). It does not explain what happens to the new list's name or the return value, but with annotations covering the mutation/destructive profile this is solid disclosure.

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 front-loaded sentence that states the action, the copied contents, and the placement with zero filler. Every clause earns its place.

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 one-parameter duplication tool with no output schema, the description covers what is copied and where it lands, which is most of what an agent needs. It leaves minor gaps around the resulting list's naming and whether the copy is a full clone, but is broadly complete.

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 0% for the single listId parameter, so the description must carry meaning, and it only implies listId as the source list via 'Copies a list' and 'same board'. It never names or clarifies the parameter, though for a single obvious identifier the gap is minor.

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?

States a specific verb (Copies) and resource (a list with its open cards), and the parenthetical enumerates exactly what is carried over (content, dates, labels, checklists). This clearly distinguishes it from duplicate_board and duplicate_task by resource scope, though it does not name those siblings directly.

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?

There is no guidance on when to use this tool versus create_list, duplicate_board, duplicate_task, or manually adding cards. No prerequisites or exclusions are given, so the agent must infer usage entirely.

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