Delete Collection

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

The description is consistent with the annotations (destructiveHint=true, idempotentHint=true, readOnlyHint=false) but only because it simply says 'Delete collection.' It adds no behavioral detail beyond the annotations—nothing about what data is removed, whether deletion is reversible, or how the `confirm`, `overwrite`, and document-related parameters affect behavior.

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?

It is short and front-loads the deletion action, but the second sentence ('Manage collection management operations') is filler that does not earn its place. The first sentence mostly repeats the tool name and title.

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 mutation tool with seven parameters, the description is incomplete: it omits confirmation behavior, deletion scope, and the role of unexpected document-related parameters. Annotations cover the basic safety profile and an output schema exists, but operational context is still 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%, so the schema is the primary source for parameter documentation and the baseline is 3. The description itself adds no meaning about parameters; notably it does not explain why document ingestion parameters appear on a delete tool.

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 restates the tool name ('Delete collection') and adds only a vague domain label plus the tautological 'Manage collection management operations.' It does not distinguish this from siblings such as vector_create_collection beyond the obvious verb, and a reader gains no addition over the 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?

There is no guidance on when to use this tool, when not to, or what alternatives exist. For a destructive collection operation, it also gives no prerequisites or confirmation guidance, leaving all routing and safety reasoning to the agent.

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