create_collection

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

Annotations already declare this is a non-readOnly, non-destructive, non-idempotent write. The description adds valuable context by stating options are forwarded to the underlying 'create' command, which tells an agent that server-side create semantics apply. It omits what happens if the namespace already exists, required permissions, and whether partial option dictionaries are merged or rejected.

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?

Two sentences, front-loaded with the action and then the option syntax. The examples are compact and each earns its place by illustrating a distinct option class, though the run-on example list could be slightly tighter.

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?

With annotations covering the safety profile and no output schema needed, the main remaining gaps are behavioral: no statement about duplicate-name failure, no defaulting rules for database/connection, and no indication of what the call returns. Adequate for a simple create, but an agent must guess at the target namespace.

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 carries the load. It does compensate well for the 'options' parameter with four concrete example shapes (validator, capped, timeseries, viewOn/pipeline), but leaves 'database' and 'connection' completely unexplained and does not clarify whether 'name' accepts a namespaced form.

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?

States a specific verb and resource ('Create a collection or view'), and the view distinction plus the option examples make clear this covers both plain collections and views — enough to separate it from siblings like create_index, rename_collection, or insert_documents.

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 mention of viewOn/pipeline implies when the view path applies, but there is no explicit 'use this when...' guidance, no note on which connection/database the collection lands in, and no mention of alternatives such as run_command for raw create commands.

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