Create Collection

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

Discloses mutation (MUTATES), get-or-create idempotency, and folder derivation from name. Annotations already hint non-read-only and non-destructive; description adds concrete details like 'never errors on duplicate' and auth requirement.

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 sentences, front-loaded with clear purpose, no unnecessary words. Each sentence adds critical information: function, mutation, idempotency, nesting, and auth.

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 the tool has one parameter, annotations, and an output schema, the description covers all necessary context: behavior, naming rules, auth, and duplicate handling. No gaps.

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?

Single parameter 'name' is fully described; schema coverage is 100% but description adds value by explaining nesting convention with '/', which is not evident from schema alone.

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 tool creates a new named collection, specifies mutation behavior, and distinguishes from siblings like list_collections and add_to_collection by explaining get-or-create and nesting.

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?

Provides explicit usage context: when to create a collection, behavior on duplicates, nesting with '/', and required auth key. Implicitly suggests when not to use (e.g., if you need to list collections, use sibling).

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