add_item

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

The description only mentions 'best-effort' for file attachment, but lacks disclosure of other behaviors (e.g., duplicate handling, permissions, side effects). With no annotations, the description carries full burden but is insufficient.

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 sentences, front-loaded with the primary action, and no unnecessary words. Every sentence serves a purpose.

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 the complexity of adding an item with many fields and optional attachments, and the presence of an output schema (which covers return values), the description still lacks usage guidelines and behavioral context, making it incomplete.

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 description adds value by linking the attachment_paths parameter to file attachment, but does not explain the fields parameter beyond schema. Schema has some descriptions (item_type examples) but coverage is low, so description partially compensates.

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 ('Add an item') and the resource ('to Zotero'), with an additional note about optional file attachment. This distinguishes it from siblings like add_item_to_collection and attach_file.

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 use this tool versus siblings such as add_item_to_collection or attach_file. The description does not provide context on prerequisites or alternatives.

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