card_checklist_create

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

No annotations are provided, so the description carries the full burden. It states the action but omits critical behavioral details: required permissions, what happens if the card is not found, whether copying includes item states, and what is returned (no output schema). Only the minimal 'this is an add operation' is communicated.

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 entire description is a single front-loaded sentence with zero wasted words. It is efficient and easy to parse, though its extreme terseness borders on under-specification for a mutation tool.

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 mutation tool with no annotations and no output schema, the description is incomplete. It does not cover permissions, error conditions, side effects, or what the response contains, leaving significant ambiguity for an agent that needs to call it safely.

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 parameter definitions already fully document cardId, name, and sourceChecklistId. The description adds only that the copy is 'optional', which is a slight value-add but largely redundant with the schema baseline.

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 states a specific verb and resource ('adding a new checklist to an existing card') and notes the optional copy source, making the purpose clear. It does not explicitly differentiate from sibling tools like card_checklists or card_checklist_update, but the action is distinct enough to avoid confusion.

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 phrase 'Use when adding a new checklist to an existing card' gives explicit guidance on when to invoke the tool. However, it provides no exclusions or alternatives (e.g., when to use card_checklist_update instead of creating), which prevents a 5.

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