delete_items

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

With no annotations provided, the description carries the burden of disclosing behavioral traits. It explicitly mentions the destructive nature ('permanently'), the trash behavior, the 50-item limit, and the safety-critical environment variable requirement. This is informative, though it could further clarify error handling if the env var is missing.

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 two concise sentences with front-loaded action and no wasted words. It efficiently conveys purpose, limit, and prerequisite.

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 one-parameter destructive tool, the description adequately covers purpose, safety requirement, and operational limits. No output schema exists, but return values are not critical for a delete operation. It lacks explicit success/failure behavior but is otherwise 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?

The input schema already describes the item_keys array with max and min limits and an example, so coverage is 100%. The description adds no new semantic meaning beyond repeating the 50-key limit. Thus the baseline score of 3 is appropriate.

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 action ('Delete'), the resource ('items from your Zotero library'), and the effect ('permanently (moves to trash)'). It distinguishes from sibling tools like delete_collection by specifying items, making the purpose unambiguous.

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 for when to use the tool: deleting items with up to 50 keys per call, and the prerequisite of UNSAFE_OPERATIONS env var. It does not explicitly name alternatives (e.g., delete_collection) but the usage context is sufficiently clear.

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