Delete Container

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

Annotations already mark destructiveHint=true, so the destructive nature is known. The description adds valuable context: 'CONFIRMATION REQUIRED' and 'after existing child/content/Inbox guards', which explain operational safeguards beyond the annotation. It does not contradict 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 a single sentence with every clause adding value. It front-loads the safety warning 'CONFIRMATION REQUIRED' and concisely communicates irreversibility and guards without redundancy.

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 delete tool with one parameter and strong annotations, the description is complete. It covers the destructive nature, the need for confirmation, and the existence of guards. It does not elaborate on error cases or return values, but those are not essential given the simplicity.

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 schema has one parameter (container_id) with 0% description coverage, and the description does not explain it. However, the parameter name is self-explanatory and the schema already provides type and format (uuid). The description adds no extra semantic value for this parameter.

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 tool's purpose: 'permanently and irreversibly delete a Container'. It uses a specific verb ('delete') and resource ('Container'), and distinguishes from related operations like archiving by emphasizing irreversibility and guards.

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 implies this tool is for permanent deletion but does not explicitly compare it to alternatives such as archive_container or restore_container. The 'CONFIRMATION REQUIRED' note signals a prerequisite (user confirmation) but provides no direct when-to-use vs alternatives guidance.

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