collection_create

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

Since annotations are absent, the description carries the full burden of behavioral disclosure. It conveys only that the tool 'creates' a collection, but does not disclose what happens on duplicate names, whether notebook_ids are validated against existing notebooks, what side effects occur, or any error behavior. There is nothing misleading, but there is no behavioral nuance beyond the verb itself.

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 compact and front-loaded: a single, plain purpose sentence followed by a short Args block. No filler, from any word, and the structure is appropriately minimal for a simple two-parameter tool.

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 that this is a simple two-parameter create operation and that an output schema provides return information, the definition is minimally viable. However, it lacks broader context such as what a 'collection' is semantically, how it relates to notebooks, or any potential pitfalls (e.g., constraints on the name or behavior with invalid notebook_ids).

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 schema itself has 0% description coverage, so the parameter semantics are introduced to compensate. The Args section does add value for notebook_ids — it explains the array contains UUIDs and that they are 'to include in the collection' — but the name parameter is glossed only as 'Name of the collection,' which nearly restates the property name and adds little semantic content.

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 opening sentence 'Create a new collection.' states a specific verb (create) and a specific resource (collection). This clearly distinguishes it from sibling tools like collection_list, collection_edit, collection_delete, and collection_set_emoji, which each have a different operation on the same resource.

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 provides no guidance on when to use this tool versus other collection or notebook tools. It does not mention common use cases, preconditions (e.g., whether notebooks must exist before being referenced), or situations where a sibling tool such as collection_edit should be used instead.

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