create_collection

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

With no annotations provided, the description carries the full behavioral burden but only says it creates something. It omits whether the operation is idempotent, what permissions are needed, how parentId nesting affects visibility, or whether duplicate titles are allowed.

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?

A single front-loaded sentence with zero filler. Nothing redundant or padded.

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?

For a four-parameter create tool with nested fieldDefinitions and no annotations or output schema, the description is minimal but the rich schema documentation covers parameter meaning. The main gap is behavioral context (nesting effects, permission needs), which nothing else supplies.

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 100%, so title, parentId, displayFields, and fieldDefinitions are all documented in the schema with examples (e.g., displayFields showing ["title", "createdAt"]). The description adds nothing beyond what the schema already conveys, so the baseline 3 applies.

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 (create) and resource (collection), plus the organizing intent. Although it doesn't name a sibling explicitly, the resource 'collection' clearly separates it from create_note in the sibling list.

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 create a collection versus using list_collections/update_collection, nor any prerequisite context (e.g., that a collection must exist before notes can be filed into it). Usage must be inferred entirely.

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