delete_item

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

The annotation already declares destructiveHint=true and readOnlyHint=false, and the description reinforces this by calling the action destructive and instructing confirmation. It adds a user-confirmation requirement, but does not disclose additional behavior such as whether deletion is permanent, cascades to related data, or requires special permissions. With annotations covering the core safety profile, this is an adequate but not rich disclosure.

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 extremely concise: a single clear action statement followed by the critical safety warning. Every word earns its place, and the destructive warning is front-loaded, making it hard to miss.

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 simple three-parameter delete operation, the safety guidance is present and the action is clear. However, the complete absence of parameter semantics and lack of any output/return information leaves meaningful gaps. The description is minimally viable but not thorough for an agent invoking it without additional 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?

Schema description coverage is 0%, and the description does not explain itemId, boardId, or projectId or how they relate to the item being deleted. The agent receives no help understanding what values to supply or why all three IDs are required.

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 the verb ('Delete') and the resource ('an item'), which distinguishes it from sibling tools like delete_board, delete_column, and delete_comment. There is no ambiguity about what operation this tool performs.

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 an important usage constraint: it is destructive and requires user confirmation. However, it does not explain when to prefer this tool over alternatives like update_item or delete_comment, nor does it describe preconditions such as whether the item must exist or be in a certain state.

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