checklists_items_delete

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 merely repeats the action implied by the name ('Delete') without adding important context such as irreversibility, permission requirements, or potential cascading effects. The description adds no safety or side-effect information.

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 immediately conveys the tool's purpose with no unnecessary words. It is well-structured and front-loaded, consistent with best practices for simple delete operations.

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 simple delete tool with two well-documented parameters and no output schema, the description is sufficiently complete. It conveys the core action and resource, though it could optionally mention whether the deletion is permanent or if any response is expected, but such details are not critical for usability here.

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%, as both checklist_id and checklist_item_id have descriptions. The tool description adds no extra parameter meaning beyond the schema, which itself adequately documents the two required IDs, so a baseline score of 3 is appropriate.

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 action ('Delete') and the specific resource ('an item from a ClickUp checklist'), making it unambiguous and distinguishing it from siblings like checklists_delete (which deletes a whole checklist) and checklists_items_create/update.

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 its use by stating it deletes an item, but it does not explicitly mention when to use this tool instead of alternatives such as deleting the entire checklist. No exclusions or alternative tool references are provided, leaving the context to be inferred from the name.

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