delete_collection

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

No annotations are provided, so the description carries the full burden. It discloses a key behavioral trait: deleting the collection also deletes all its vectors (cascading destructive behavior). It does not mention irreversibility or permissions, but the explicit 'all its vectors' is a meaningful disclosure beyond the basic delete action.

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 appropriately concise with the primary action front-loaded and a clear parameter explanation. The 'Args' line is slightly redundant given the schema but efficiently captures the param semantics. No unnecessary words.

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 single-parameter destructive operation with an output schema present, the description covers the action and the parameter adequately. It could optionally mention error conditions (e.g., if collection doesn't exist), but that's not required for basic completeness. The major side effect (deleting all vectors) is explicitly disclosed.

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 0% description coverage for the 'name' parameter, but the description compensates with an 'Args' section stating 'name: Collection name to delete.' This adds clear semantic meaning to the parameter, fulfilling the need beyond the schema.

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 opens with 'Delete a collection and all its vectors,' which clearly states the action (delete) and the resource (collection) with a specific scope (all vectors). This distinguishes it from sibling tools like delete_document, which targets individual documents, and create_collection/list_collections, which handle collection lifecycle.

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 usage: it's for deleting a collection. However, it does not explicitly state when to use this tool versus delete_document or when not to use it. The guidance is implied by the name and context rather than stated, so it meets the minimum but lacks exclusionary guidance.

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