delete_item

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Delete' implies a destructive mutation, it doesn't specify whether deletion is permanent or reversible, what permissions are required, whether it affects related data, or what happens on success/failure. This is inadequate for a destructive operation with zero annotation coverage.

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 with zero wasted words. It's appropriately sized for a simple deletion operation and front-loads the essential information (action, resource, identifier type).

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 destructive mutation tool with no annotations, no output schema, and 0% parameter documentation, the description is incomplete. It doesn't address critical context like what 'delete' means operationally, what happens to the item, error scenarios, or return values. The presence of many sibling tools (especially other deletion operations) increases the need for clearer differentiation.

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?

With 0% schema description coverage for both parameters, the description doesn't compensate at all. It mentions 'numeric ID' which corresponds to the 'id' parameter, but provides no context about the 'listName' parameter (what lists exist, format requirements, or relationship to other tools). For a tool with 2 undocumented parameters, this is 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 clearly states the action ('Delete') and resource ('a list item'), specifying it's done 'by its numeric ID'. It distinguishes from siblings like delete_list (which deletes entire lists) and delete_column (which deletes columns), but doesn't explicitly differentiate from update_item or other item-related tools.

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 provides no guidance on when to use this tool versus alternatives like update_item (which might archive instead of delete) or delete_list (which deletes entire lists). It doesn't mention prerequisites, error conditions, or typical use cases for item deletion versus other operations.

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