checklists_items_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 discloses that the tool supports optional assignee and resolved status, which is helpful, but it does not mention side effects, required permissions, error behavior, or prerequisites beyond the parameters. The description is adequate for a simple create operation but lacks deeper 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 a single, focused sentence that front-loads the core purpose and adds optional parameter context. Every word earns its place, and it is appropriately sized for a tool with a simple, well-documented schema.

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 simplicity, the description covers the essential function and optional parameters. There is no output schema, so the description need not explain return values. It is complete enough for an agent to select and invoke the tool correctly, though additional context about prerequisites (e.g., needing an existing checklist) could enhance completeness.

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% with descriptive parameter text, so the baseline is 3. The description adds that assignee and resolved are 'optional,' which reinforces the schema's required-field list, but it does not significantly enhance understanding beyond what the schema already provides.

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 tool's purpose with a specific verb and resource: 'Create a new item in a ClickUp checklist.' This distinguishes it from sibling tools like checklists_items_update and checklists_items_delete, and it correctly scopes the operation to checklist items rather than checklists themselves.

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 implies when to use the tool (to create checklist items) but offers no explicit guidance on when not to use it or which alternatives might be more appropriate (e.g., creating a checklist vs. an item). There are no stated exclusions or preconditions, so usage context is only implicit.

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