create_collection

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

With no annotations, the description carries the burden of behavioral disclosure. It mentions that it creates a collection, optionally nests it, and returns the key and name. However, it does not discuss permissions, duplicate handling, or failure modes. This is adequate but not rich.

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 three sentences, front-loaded with the core action, and every sentence adds value: the action, the optional nesting, and the return value usage. No fluff 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?

For a simple create tool with no output schema, the description covers the essential context: what it does, the return value, and a downstream use case. It lacks explicit instructions on when not to use it, but given the simplicity, it is nearly complete. A score of 4 reflects that it could mention edge cases or requirements but is mostly sufficient.

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 coverage is 100% with both parameters documented ('name' and 'parent_collection'). The description adds minimal extra meaning beyond the schema, except noting the nesting behavior and the return key's use with add_items_by_doi. Since the schema already provides descriptions, a baseline of 3 is appropriate.

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 a new collection (folder) in your Zotero library.' It distinguishes from sibling tools like delete_collection and get_collections by specifying the create operation and the ability to nest under a parent collection. The return value is also mentioned, making the purpose 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 provides clear context on when to use this tool: to create collections and organize imported papers. It explicitly mentions using the returned key with add_items_by_doi, which implies a workflow. It does not explicitly list alternatives or exclusions, but the context is strong enough to guide an agent.

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