Create Zotero item

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

Annotations already indicate a non-read-only, non-destructive operation, so the description adds the explicit authentication requirement, which is useful. However, it does not disclose what happens on success or failure, required itemType constraints, or where the created item appears. It provides moderate context but not rich behavioral detail.

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 concise sentence with no filler and the key action is front-loaded. It is efficient as a purpose statement, though it omits substantial necessary detail; that tradeoff is better captured in other dimensions.

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 tool with five parameters, two required, nested objects, no enum constraints, no output schema, and zero schema descriptions, a one-sentence description is far from adequate. An agent would not know accepted itemType values, how to structure fields or creators, or what a successful response looks like. The description is not sufficient for correct 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?

Schema description coverage is 0%, so the description carries the burden of explaining parameters. It mentions none of the five parameters: itemType, fields, creators, tags, or collectionKeys. An agent cannot infer what values to provide or how to structure the nested fields and creators objects.

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 states a clear verb (Create), a resource (Zotero item), and the access context (authenticated Research Workbench extension). It is understandable on its own, but it does not distinguish 'item' from sibling tools like zotero_create_note, zotero_create_collection, or zotero_attach_link, so it earns 4 rather than 5.

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?

There is no guidance on when to use this tool versus alternatives such as zotero_update_item, zotero_create_note, or zotero_create_collection. The only contextual hint is 'authenticated', which is a prerequisite rather than a selection criterion. No when-to-use or when-not-to-use information is provided.

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