empty_trash

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

With no annotations, the description carries the full burden of disclosing behavior. It fails to mention that emptying the Trash permanently deletes all items and is irreversible, which is critical safety context for a destructive operation.

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 very concise and free of fluff, but it is under-specified. While a one-sentence description is appropriate for a simple no-arg tool, this sentence omits essential information about permanence and scope, making it too minimal to be fully effective.

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?

Despite the tool's low complexity and presence of an output schema, the description is incomplete for a destructive action. It does not state that all items are removed permanently or that the operation cannot be undone, which are essential contextual details.

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 tool has zero parameters, so the baseline of 4 applies. The description does not need to explain parameter meanings, and no parameters are left undocumented.

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 'Empty the Trash' uses a specific verb and resource, clearly indicating the action of removing all items from the Trash. It is distinguishable from sibling tools like move_to_trash, though it does not explicitly describe the permanent deletion nature.

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?

There is no guidance on when to use this tool versus alternatives such as move_to_trash, nor any mention of prerequisites or warnings. It does not say 'use this to permanently delete all trashed items' or caution against selective deletion.

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