Delete Items

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

Annotations already indicate destructiveHint=true, so the agent knows it's a write operation. The description adds valuable context: soft-delete is the default, hard delete requires permanent=true, and the tool returns per-id results for partial failures. This clarifies exactly what happens and how results are reported, going beyond the annotations.

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 only two sentences and covers the core information: what the tool does, default behavior, optional parameter effect, and return behavior. Every word serves a purpose, with no fluff.

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 batch delete tool with two parameters and no output schema, the description covers the essentials: batch scope, delete modes, and partial failure reporting. It also implicitly distinguishes from the singular sibling. No additional information is necessary.

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 coverage is 100%, so the schema already describes both parameters. The description mentions 'by id' and 'set permanent=true', which largely restates the schema's own descriptions. It does not add significant new nuance about parameter values or constraints beyond what the schema provides, so the value added is minimal.

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 'Delete multiple vault items by id in one session,' specifying the action (delete), resource (vault items), and scope (multiple items). It distinguishes from the sibling 'keychain_delete_item' by emphasizing batch deletion, and differentiates between soft and hard delete via the 'permanent' parameter.

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 clear context on when to use the tool (batch delete) and explains the default behavior (soft-delete) and the alternative (hard delete with permanent=true). It also notes that partial failures are visible, which informs error handling. However, it does not explicitly state when not to use this tool or mention alternatives like the singular delete sibling.

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