Delete an item entirely

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

With no annotations, the description carries full responsibility. It explicitly states the irreversible nature ('This cannot be undone') and the cascading unlinking effect, which are critical behavioral details. It doesn't mention permissions or error cases, but for a destructive op the irreversibility warning is strong.

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 entire description is two tight sentences. The first states the action, the second delivers the critical irreversible warning. No wasted words, and the most important fact (cannot be undone) is 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?

For a one-parameter delete tool with no output schema, this description provides adequate context: the action, the side effect of unlinking, and the irreversible nature. It misses a bit of guidance on parameter semantics and behavior when the item doesn't exist, but overall it is sufficiently complete for a straightforward destructive operation.

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 has zero description coverage, and the description does not mention the 'itemId' parameter at all. The agent must infer that itemId is the identifier to delete, which is a risky assumption. The description could have at least confirmed that itemId is the target item to remove.

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 starts with a specific verb+resource: 'Deletes an item from the library.' It adds distinct scope by explaining it unlinks from every category/list, which clearly differentiates it from siblings like 'remove_item_from_category' or 'delete_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?

The description tells what it does but offers no guidance on when to choose it over alternatives like 'update_item' or 'remove_item_from_category.' It implies deletion of the entire item, but there is no explicit context for when this should be used instead of related tools.

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