create_collection

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

With no annotations provided, the description carries the full burden. It discloses an admin permission requirement, but doesn't describe side effects, validation, failure modes, or what the created collection looks like. For a write operation, this is insufficient transparency.

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 highly concise, consisting of two short sentences with no filler. It front-loads the action and includes a permission note. However, it is under-specified, which makes it tight but not necessarily well-rounded. Still, from a pure conciseness standpoint, it earns a 4.

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?

Despite having an output schema, the tool's complexity (a nested object parameter) and lack of meaningful schema constraints place the burden on the description. The description fails to explain the structure or requirements of the collection object, and gives no context about the creation process. This is far from complete for a create operation.

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 has one parameter, `collection`, an object with additionalProperties: true. The description provides zero information about what properties the collection object should have, and with 0% schema description coverage, the parameter semantics are entirely unexplained. The description does not compensate for the schema's lack of detail.

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 uses the specific verb 'Create' with the resource 'collection,' clearly identifying the operation. It doesn't elaborate on what a collection is or how it differs from related tools like update_collection, but the action is unambiguous. The addition of 'Requires ADMIN' adds a permission context, but the core purpose is clear.

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?

No guidance on when to use this tool vs alternatives. It doesn't mention that this is for creating new collections while update_collection is for modifying existing ones, nor any prerequisites beyond admin. There is no explicit when-to-use or exclusions.

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