delete_item

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

With no annotations provided, the description must carry behavioral disclosure, and 'permanently' at least signals irreversibility and destructive intent. However, it does not mention side effects, authorization requirements, or whether related data is affected, leaving part of the burden unmet.

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 five words, front-loaded with the verb and object, and contains zero filler. Every word earns its place, especially 'permanently,' which adds an important behavioral qualifier.

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?

Although the API surface is simple with one required parameter and no output schema, the description leaves unstated what qualifies as a tracked item, whether deletion cascades to associated records, and what success or error responses look like. It is adequate for basic invocation but not fully self-sufficient.

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 coverage is 100%, so the single parameter itemId is already documented as 'Item ID.' The description adds only that the target is a 'tracked item,' providing light domain context but no additional syntax, format, or relationship semantics.

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 uses a specific verb ('Delete') plus a clear resource ('a tracked item'), making the operation unambiguous. It distinguishes from sibling item tools like create_item and update_item, as well as from delete_* tools targeting other resources.

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?

There is no guidance about when to use delete_item versus alternatives, nor any exclusion criteria or prerequisites. The intended use is only implied by the verb and resource name.

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