delete_checklist_item

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

Annotations already signal destructiveHint=true, idempotentHint=true, and readOnlyHint=false. The description adds no additional behavioral context (e.g., effect on related entities, error handling). It does not contradict annotations, so a 3 is appropriate.

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 sentence, but it sacrifices necessary detail for brevity. It could be slightly longer to include behavioral notes without becoming verbose.

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 destructive nature (destructiveHint=true) and lack of output schema, the description should clarify what happens upon deletion (e.g., success behavior, persistence, return value). It omits critical context for safe 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 0%, and the description provides no explanation for the three required parameters (list_id, task_id, item_id). Without clarification, the agent must infer meanings from parameter names alone, which may be insufficient.

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 'Delete a sub-item' uses a specific verb and resource, clearly indicating the action. It is distinguishable from sibling tools like delete_task and create_checklist_item, though it could explicitly name 'checklist item' instead of 'sub-item'.

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?

No guidance on when to use this tool versus alternatives (e.g., delete_task, batch_delete_tasks). No prerequisites or context for usage are provided, leaving the agent without decision criteria.

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