Create a collection

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

Annotations already declare this as a non-read-only, non-idempotent, non-destructive, open-world write, so the safety profile is covered elsewhere. The description adds that it returns the created collection, which is genuinely useful given there is no output schema, but says nothing about auth requirements or whether duplicates are 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?

Front-loaded with the core action and then a compact Args/Returns breakdown; every clause carries information. The list format is mechanical but wastes no words.

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 no output schema, the "Returns: the created collection" line fills the return-value gap, and all four arguments are accounted for at least minimally. Only prerequisites/permission context is missing, which is a modest omission for a simple create tool.

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 only 50% (name and color are documented; private and description are not), yet the description compensates by labeling description as optional Markdown and private as defaulting to false, plus giving a hex example for color. This adds meaning the schema does not carry.

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." The resource is distinct from siblings like outline_list_collections and outline_create_document, so an agent can tell what object is produced. However, it does not explicitly contrast itself with the other create/collection tools, so it falls short of the top band.

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?

There is no guidance on when to use this tool versus alternatives, nor any prerequisites or preconditions (e.g. whether the collection must not already exist, or whether permission is needed). The reader is left to infer usage entirely from the name.

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