delete_item

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

No annotations are provided, so the description carries the burden. It explicitly discloses the destructive, irreversible nature with "Permanently delete" and requires user confirmation. It does not mention permissions or cascade effects, but the core behavior is transparent enough.

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 short sentences with no filler: the first conveys the action and index semantics, the second adds a necessary safety gate. Perfectly front-loaded and every sentence earns its place.

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 essential behavioral context (permanence, user confirmation, zero-based indexing) is covered; the output schema covers return values. The only minor gap is that "formId" is not explicitly described, though it is reasonably inferable from the parameter name and sibling tool context.

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 no parameter descriptions, and the description compensates only partly. It adds meaning to the "index" parameter by specifying "zero-based index," but it does not explain the "formId" parameter, leaving it to be inferred from context.

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 states a specific action and target: "Permanently delete an item by zero-based index." It clearly identifies the resource type and deletion mode, and the verb "delete" separates it from sibling tools like "move_item" or "add_*" tools.

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 a clear operational precondition: "Confirm the exact item with the user first." This gives context for safe usage and implies that the tool is for destructive, user-approved removals rather than add/move operations. It does not explicitly name excluded alternatives, but the guidance is sufficiently clear.

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