delete_list_item

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

With no annotations, the description carries the full burden of behavioral disclosure. It clearly warns that the action permanently removes the item, which is critical destructive-behavior information. It also contrasts with checking off to clarify the effect. Slight room remains for additional details (e.g., reversibility, side effects), but for this simple tool it is adequately transparent.

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 well-structured with a clear topic sentence, a 'Use this when' list, a parameter list, and a note for an alternative. Every sentence earns its place, and the layout makes key information easy to scan.

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?

This is a low-complexity tool with two simple parameters and no output schema. The description provides the core purpose, usage conditions, parameter meanings, and permanent/deletion behavior. It is complete enough for an agent to decide when and how to invoke it correctly.

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 input schema already documents both parameters with descriptions at 100% coverage. The description essentially repeats the parameter names and their purpose, adding no extra meaning beyond what the schema provides. The baseline of 3 applies here.

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 opens with a specific verb and resource: 'Remove an item from a list.' It clearly identifies the tool's function and distinguishes it from siblings by explicitly noting that checking off an item should use update_list_item instead.

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 'Use this when' section provides concrete scenarios (removing an item added by mistake, deleting instead of completing). It also explicitly names the alternative tool and usage pattern (update_list_item with status='completed'), making when-to-use and when-not-to-use unambiguous.

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