collection_create

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

Annotations indicate this is a write operation but not destructive; the description goes beyond this by explaining what the tool configures by default (named vectors and payload indexes) and that it creates a fresh, standalone collection. It adds useful behavioral context such as the intended one-time usage per document set.

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 two sentences, front-loaded with the core action, and every clause adds useful information. There is no filler or repetition of schema details.

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 two simple parameters and an output schema, the description covers the core purpose, usage boundary, and default behavior well. A minor gap is the lack of guidance about what differentiates the presets or what happens if a collection with the same name already exists.

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, and it partially does by explaining that 'name' is a collection name tied to a new document set and 'preset' selects dense, hybrid, or multitenant. However, it does not explain what each preset actually changes or how the name should be formatted, so the parameter semantics are only partially fleshed out.

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 that this tool creates a new Qdrant collection, names the available presets, and says it configures named vectors and payload indexes by default. It also distinguishes this operation from adding documents, making its scope unambiguous.

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 explicitly says to use this tool once per new document set needing its own collection, and explicitly tells the agent not to use it for adding documents to an existing collection, directing it to ingest_* tools instead.

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