Delete a collection

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

Annotations only declare destructive/idempotent/open-world; the description adds the soft-delete default, the 7-day grace period, when purging becomes irreversible, the GDPR/BIPA audit mode, and the confirmation refusal path. It also discloses that the operation costs no credits.

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?

Four tightly packed sentences, front-loaded with the destructive default and ending with the confirmation duty. Dense but nearly every clause carries decision-relevant information; the trailing 'Free.' is terse to the point of ambiguity.

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 destructive four-parameter tool with no output schema, the definition covers irreversibility, recoverability, refusal behaviour, and cost, leaving nothing an agent needs to call it safely.

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 baseline is 3, but the description goes beyond the schema by explaining how immediate and compliance interact with the refusal behaviour and by framing confirm_erase as a retry token rather than a plain flag.

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?

States a specific verb and resource ('Delete a collection') and immediately scopes it to everything contained in it ('every face, selfie and photo record'), which distinguishes it from the sibling delete_photo.

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?

Explicitly names the alternative restore path (restore_collection) and the window in which it works, contrasts three modes of deletion, and instructs the agent to confirm with the user before calling. It also tells the agent exactly how to recover from a confirmation_required response.

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