create-collection

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the description's job is to add extra behavioral nuance. It discloses that the database is created automatically if absent, which is beyond the annotations. It doesn't mention behavior like existing-collection handling, but that is not required given the annotations provide the safety profile.

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 short sentences that are front-loaded with the core action. Every word earns its place, and the auto-create note adds valuable context without unnecessary elaboration.

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 simple tool with two parameters, an output schema, and safety annotations, the description is adequate and covers the primary behavior. It omits edge cases like what happens if the collection already exists, but given the complexity, this is a minor gap. The presence of an output schema reduces the need to describe return values.

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 input schema covers both parameters with descriptions ('Database name', 'Collection name'), achieving 100% coverage, so the baseline is 3. The description does not enrich parameter meanings beyond the auto-create effect on the database parameter; no format, constraints, or examples are added.

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 the action: 'Creates a new collection in a database.' The verb 'creates' and resource 'collection in a database' are specific and unambiguous, distinguishing it from sibling tools like drop-collection and rename-collection. The additional note about auto-creating the database clarifies scope.

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 (when you need to create a collection) but provides no explicit when-to-use or alternative guidance. The auto-create behavior is a useful context cue, but no exclusions or comparisons to sibling tools like insert-many (which may also auto-create collections) are given.

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