create_collection

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

Annotations already disclose readOnly=false, idempotent=false, destructive=false. The description adds the folder synonym and optional parent nesting, which is useful, but it does not explain behavior around duplicate names, parent_key validation, or any side effects beyond creation.

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?

Two tight sentences with no filler. The primary action is front-loaded, and the parent option and intended use case are included directly.

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 2-parameter creation tool with annotations and an output schema, the description covers the key points: what it creates, where, and the optional parent. It could add a short note on parent_key validity or duplicate names, but nothing vital is missing for a standard invocation.

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 has no parameter descriptions, so the description must compensate. It clarifies that parent_key relates to nesting under a parent and that name identifies the new collection, but it does not specify that parent_key must reference an existing collection key or explain name uniqueness.

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 the exact operation with a specific verb and resource: 'Create a new collection (folder) in Zotero'. It also clarifies optional nesting under a parent and frames the purpose as 'organize papers into a new group', which distinguishes it from create_item and create_note.

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?

Explicitly provides a usage condition: 'Use this when the user wants to organize papers into a new group.' It gives clear context but does not mention when not to use it or name alternatives like add_to_collection or batch_organize.

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