Delete Units By Item

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

With no annotations, the description carries the full burden of disclosing behavior. 'Delete One' signals a destructive action and singular scope, but says nothing about irreversibility, cascading effects, permissions, soft-delete behavior, or response semantics. For a mutation tool, this is a substantial gap.

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?

Two words are superficially concise, but this is under-specification rather than efficient writing. A truly concise description would pack the essential resource, identifier, and usage context into a sentence, not omit all of them.

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?

The description is far too thin for a tool with two parameters, no annotations, and no stated effects. Even though an output schema exists, the description fails to identify the target resource, the role of item_id, or the consequences of deletion. This is inadequate for safe invocation.

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%, so the description must compensate, but it does not mention item_id or accept-language at all. 'Delete One' adds no meaning to the parameters; an agent cannot tell what item_id refers to or whether accept-language affects the request.

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 One' is vague: it provides a verb and singular scope but never names the resource ('unit') or the identifying mechanism ('by item'). It relies entirely on the tool name/title for meaning and does not distinguish itself from the many other delete_*_by_item tools in the sibling list.

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 on when to use this tool versus alternatives. It does not mention that this deletes a single unit by item_id, nor does it contrast with update_units_by_item, update_units_merge, or any other unit-related operation. Agents are left to infer usage entirely from the name.

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