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

Annotations declare destructiveHint=true and non-idempotent, and the description adds non-obvious behavior beyond that: the deletion is recoverable (event with restorable: true, restore_item re-creates with the same id) and the precondition failure mode (ITEM_PRECONDITION_FAILED, nothing written). It does not spell out auth requirements or a return shape, but the recovery and failure semantics are the material additions.

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?

Four short sentences, front-loaded with the operation, then recovery, then the concurrency rule. The trailing '1 request' is terse but useful cost context; nothing here is padding.

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?

With annotations covering the safety profile and an output schema handling return values, the description supplies exactly what structured fields cannot: reversibility, the sibling tools that enable restore, and the ifMatch precondition rule. Nothing needed to call this correctly is missing.

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 100%, so item, list, and ifMatch are already fully documented in the schema, including the same precondition semantics the description restates. The description adds only a light usage rule for ifMatch and no new format or value information, so the baseline 3 applies.

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?

States a specific verb and resource ('Delete an item') and immediately distinguishes itself from its siblings by naming the recovery path (list_events + restore_item) that delete_item_data and delete_list do not share. An agent can tell this apart from the other delete_* tools without opening any schema.

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?

Gives clear conditional guidance: pass ifMatch when the write is based on something you read, so the delete only fires if nobody changed the item. It does not explicitly contrast itself with delete_item_data or explain when not to delete, but the operating context is unambiguous.

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