collections_create

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

No annotations are provided, so the description carries the full burden. It only says 'Create' and gives no information about side effects, uniqueness constraints, error conditions, or whether the operation is reversible. The mention of 'schema' is ambiguous and not backed by any schema field in the input.

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 a single sentence that is direct and front-loaded with the action. There is no unnecessary wording or repetition.

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?

The tool has a nested request object and no annotations or output schema. The description is too minimal to fully guide an agent on constructing a valid request or understanding what happens after creation. The word 'schema' could mislead an agent into looking for a schema parameter that doesn't exist.

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 description adds no meaningful explanation of parameters beyond what the schema already provides. It refers to 'name and schema', but the input schema has displayName, singularName, and slug; there is no 'schema' parameter. The request object itself lacks a description, and the description does not compensate for this gap.

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 ('Create') and the resource ('a new CMS collection in a site'), which distinguishes it from sibling tools like collections_list or collections_get. The verb+resource combination is specific and unambiguous.

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 ('you use this when you want to create a collection') but provides no explicit guidance on when not to use it or how it compares to alternatives. No exclusion criteria are mentioned.

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