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

The description adds substantial behavioral context beyond the annotations: it precisely lists what is duplicated and, crucially, what is not (comments, assignees, attachments) — a real gotcha for an agent. It does not contradict destructiveHint=true, though it also says nothing about permissions or the returned object.

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?

One front-loaded sentence, verb first, with the inclusion/exclusion lists compressed into a tight trailing clause. No redundant or filler text.

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 single-parameter duplication tool with no output schema, the description covers the operation's scope well, but omits what the call returns (e.g., the new task's id) and gives no hint about the required identifier. Annotations cover the safety profile, so the remaining gap is moderate.

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?

Only one parameter (cardId, required) with 0% schema description coverage, and the description never explains it. The meaning is strongly inferable (the task to copy), so it's minimally adequate, but the description does not compensate for the coverage gap.

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) plus resource (a task) and even the placement (right below the original), then enumerates the exact fields duplicated. An agent can distinguish this from duplicate_board, duplicate_list, and create_task without opening any schema.

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 copy scope is clear, but there is no explicit when-to-use guidance or reference to alternatives (create_task, save_task_as_template, duplicate_board/list). Usage is only implied by the tool name and the sibling family.

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