delete_item

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

The description adds no behavioral information beyond what annotations already convey. Annotations include destructiveHint=true and readOnlyHint=false, so the description's 'Delete an item' is consistent but redundant. It does not disclose additional details such as irreversibility, cascading effects, or authorization requirements, which would add value beyond the structured hints.

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 (three words) and avoids verbosity, but it is under-specified to the point of being almost identical to the tool name. It does not waste words, but it also does not earn its place by adding meaningful information. This is acceptable but not exemplary conciseness.

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 tool with no output schema, the description is incomplete. It does not explain what happens on deletion (e.g., permanent removal, return values, side effects). Annotations provide the destructiveHint, but the description lacks contextual details that would help the agent understand the full impact. Given the low complexity, a bit more explanation would make it 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 input schema fully documents the single parameter 'article_id' with a description ('the id of the item'), so schema coverage is 100%. The description itself adds no parameter information, but the baseline for full schema coverage is 3; the description does not compensate with any additional semantics beyond the schema.

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 an item' clearly states the action (delete) and the resource (item), which is understandable and distinct from sibling tools like delete_item_position or create_item. However, it lacks any additional scope or specificity, such as what 'item' refers to or any qualifying conditions, so it does not fully distinguish beyond the resource name.

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. It does not mention prerequisites, use cases, or exclusions. For example, it does not say whether this tool should be used instead of delete_item_position or if it is the correct tool for deleting articles. This leaves the agent without context for selection.

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