delete_item

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the confirm=true gate and that the item id is logged, which goes beyond the schema, but it omits critical destructive-action details such as irreversibility, cascading effects on child items, permission requirements, and what happens when confirm is false or omitted. These gaps are significant for a delete tool with zero annotation coverage.

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, front-loaded with the operation and followed by the critical confirm and logging details. Every sentence earns its place with no repetition or filler.

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 output schema covers return values, and the description covers the confirm gate and logging. However, for a destructive mutation with no annotations, it should disclose irreversibility, failure modes, and permission requirements to be 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?

Schema description coverage is 0%, so the description must compensate for three parameters. It explains the confirm parameter's required value and references item_id in the logging behavior, but board_id is entirely unexplained and item_id's role is only indirectly implied. It adds partial meaning but leaves a real gap.

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 verb and resource: 'Delete any single item.' The word 'single' implicitly distinguishes it from the bulk_delete_items sibling, though no sibling is named explicitly. An agent can determine the core operation without opening the 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?

Usage is implied by 'single item' (as opposed to bulk deletion) and the confirm=true requirement, but there is no explicit when-to-use guidance, no named alternative, and no statement of when not to use it. An agent must infer that bulk_delete_items handles multi-item cases.

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