zotero_empty_trash

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

Since no annotations are provided, the description carries full responsibility for behavioral disclosure. It explicitly warns that the operation is destructive ('Permanently delete'), irreversible ('cannot be undone'), scoped to every trash item, and guarded by confirm=true. This is excellent transparency for a dangerous mutation tool.

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?

Three short sentences contain no filler, the core action and irreversible consequence are front-loaded, and the safety condition is stated last. The description is appropriately sized and easily parsed by an agent.

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 one-parameter destructive tool with an output schema, the description covers the essential operational facts: scope, irreversibility, and the confirmation guard. It could also point to restoring items as the alternative when destruction is not intended, but nothing needed to invoke the tool correctly is missing.

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 100%, and the schema already states that confirm 'Must be true to permanently delete everything in the trash.' The description's 'Requires confirm=true' reinforces the requirement but adds no new semantic information beyond what the schema provides.

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 ('permanently delete'), a specific resource ('every item in the trash'), and the all-encompassing scope ('EVERY item'), which clearly distinguishes it from siblings like zotero_list_trash and zotero_restore_items. An agent knows exactly what the tool does even without a title.

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 clearly implies when to use the tool: when the agent needs to permanently clear the entire trash. However, it does not explicitly contrast this with alternatives such as restoring items or reviewing the trash first, so the when-not-to-use guidance is left largely to inference.

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