clickup_checklist_add_item

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively communicates that this is a mutation operation (append), specifies the initial state (unresolved), describes the return value (updated checklist object with all items), and references related operations. It doesn't mention authentication requirements, rate limits, or error conditions, but provides substantial behavioral context.

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 perfectly concise with three sentences that each serve distinct purposes: stating the core operation, providing usage differentiation, and describing the return value. There's zero wasted language, and the information is front-loaded with the primary action.

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 does an excellent job covering the essential context: operation type, initial state, return value, and sibling relationships. It could potentially mention authentication requirements or error scenarios, but provides sufficient information for effective tool selection and use.

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 100%, so the schema already documents all three parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema descriptions. This meets the baseline expectation when schema documentation is complete.

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 specific action ('Append a new item'), target resource ('existing ClickUp checklist on a task'), and initial state ('starts unresolved'). It distinguishes from siblings by naming clickup_checklist_update_item and clickup_checklist_delete_item for different operations.

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 explicitly provides when-to-use guidance by stating this is for adding new items, and when-not-to-use by directing to specific sibling tools for editing/resolving (clickup_checklist_update_item) and removing (clickup_checklist_delete_item). It clearly defines the tool's role within the checklist item lifecycle.

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