collection_delete

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

Beyond the annotations, the description discloses that deletion is permanent, removes all data, requires confirm_name to exactly match name, and is blocked in read-only server mode. This is strong behavioral context and 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?

Three concise, front-loaded sentences. Every sentence adds useful information: permanent deletion, destruction, confirmation, read-only block, and user-confirmation guard. No redundant text.

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 two-parameter destructive tool with annotations and output schema, the description covers all essential behavior, including irreversibility, the guard to prevent accidental deletion, and operating restrictions. The agent can safely invoke this tool without needing further context.

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 0%, so the description must compensate. It clarifies that confirm_name must exactly match name and that name identifies the Qdrant collection. It could list each parameter separately, but the critical confirmation relationship is explicit and sufficient.

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 uses a specific verb and resource: 'Permanently deletes a Qdrant collection and all its data'. This clearly distinguishes collection_delete from siblings like collection_create, collection_list, collection_info, and document_delete.

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?

It explicitly states when to use the tool: only after the user explicitly confirms deletion. It also mentions the read-only mode block and confirmation-match requirement. It does not mention alternative actions like backup or snapshot-restore, but for a destructive delete the main safety guidance is clear.

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