delete_item

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

No annotations are provided, so the description must carry behavioral disclosure. It only says 'Delete', conveying irreversibility implicitly, but lacks explicit warnings about consequences, required permissions, or whether deletion is permanent. This is insufficient for a destructive tool.

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 sentences, zero waste. The purpose is stated first, followed by a critical prerequisite. Perfectly concise and front-loaded.

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 covers purpose and a key prerequisite, but for a delete operation it lacks details on irreversibility, expected return value, permissions, and error handling. Given the simple parameter set and no output schema, the description is adequate but not fully 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 schema already describes all three parameters thoroughly (100% coverage). The description adds value by explaining where to obtain name and scopeId values ('as shown in scan_inventory results'), which is meaningful guidance beyond the schema alone.

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 'Delete a Claude Code configuration item' with a specific verb and resource. It also directs to run scan_inventory first, which helps distinguish this deletion tool from sibling tools like move_item or list_destinations.

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 explicitly tells the agent to run scan_inventory first to see available items, providing clear context for when to use this tool. However, it does not mention when not to use it or any alternatives, but for a delete operation this is sufficient.

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