checklist-deleteItem

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

The description states that the tool 'Deletes' an item, which implies a destructive action, but it does not disclose any side effects, required permissions, or whether the operation is reversible. With no annotations provided, the description carries the full burden and falls short.

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 very short and to the point. The inclusion of '(Tags: Cards)' is somewhat extraneous but does not detract significantly. It could be more concise by removing the tag line.

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 a simple tool with one parameter and no output schema, the description should at least clarify the parameter and mention any side effects. The current description is too minimal to be considered complete.

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?

The only parameter, 'checklistItemPublicId', has no description in the schema (0% coverage). The tool description does not explain its purpose, format, or how to obtain it, leaving the agent to infer from context.

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 ('Deletes a checklist item') and identifies the resource. While it distinguishes from sibling 'checklist-delete' which deletes the entire checklist, it does not explicitly differentiate from other item operations like update; however, the verb 'delete' is unambiguous.

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 is provided on when to use this tool versus alternatives such as 'checklist-updateItem' or 'checklist-delete'. There is no mention of prerequisites (e.g., obtaining the item's public ID) or when not to use it.

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