card-duplicate

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

No annotations are present, so the description must disclose behavior. It claims the options are 'optional', but the schema requires them (copyLabels, copyMembers, copyChecklists). This misrepresents the tool's behavior and contradicts the schema. No mention of side effects or permissions.

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 very concise (one sentence plus a tag), but it sacrifices accuracy and completeness. While brevity is good, the misstatement about optional options makes it less useful.

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?

Given the tool's complexity (nested object with multiple parameters, no output schema), the description is incomplete. It does not explain what happens after duplication, the new card's identity, or any constraints. The agent lacks critical context for proper invocation.

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 50% (only requestBody has a description), but the description adds no parameter explanations. It uses 'optional options' which is misleading since the booleans are required. No additional 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 verb 'Duplicates' and specifies the resource 'a card to a target list', making the action unambiguous. It distinguishes from sibling tools like card-create and card-update by focusing on duplication.

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 no guidance on when to use duplication over other card operations, nor does it mention prerequisites or alternatives. The agent must infer usage from the tool name alone.

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