delete_collection

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It helpfully adds that 'All documents in the collection will also be deleted,' which is crucial context beyond the basic 'delete' action. However, it doesn't address other important behaviors: whether deletion is permanent or reversible, what permissions are required, if there are confirmation prompts, or what the response looks like (success/failure indicators).

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 extremely concise—two short sentences that communicate the core action and a critical side effect. Every word earns its place: 'Delete a collection' establishes the purpose, and 'All documents in the collection will also be deleted' provides essential behavioral context. There's no redundancy or unnecessary elaboration.

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?

Given this is a destructive operation with no annotations and no output schema, the description is incomplete. It covers the basic action and cascading deletion effect but misses important context: whether the operation is reversible (checking sibling tools shows 'restore_document' but no collection restoration), what permissions are needed, error conditions, or response format. For a high-stakes delete tool, more behavioral transparency would be expected.

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 has 1 parameter with 0% description coverage, so the description must compensate. While it doesn't explicitly mention the 'collectionId' parameter, it implies its necessity by stating 'Delete a collection'—the agent can infer that identifying the collection is required. For a single-parameter tool where the parameter's purpose is obvious from context, this is adequate. However, it doesn't specify the UUID format or provide examples.

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') and resource ('a collection'), making the purpose immediately understandable. It distinguishes this from sibling tools like 'delete_document' by specifying it operates on collections rather than individual documents. However, it doesn't explicitly differentiate from other collection-related tools like 'archive_document' or 'list_collections' beyond the obvious action difference.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (like needing collection ownership), when not to use it (e.g., for temporary removal), or direct alternatives among siblings (like 'archive_document' for documents or whether collections can be archived). The user must infer usage from the tool name alone.

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