Add Item From Metadata

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the agent knows this is a mutating but non-destructive operation. The description adds useful behavioral context: the Zotero item template determines which fields are accepted, preventing invalid cross-type metadata. However, it doesn't disclose what happens on validation failure, whether partial metadata is accepted, or what the response contains. With annotations covering the basic safety profile, a 3 is appropriate.

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?

Three short paragraphs with no filler. The core purpose is front-loaded in the first sentence, followed by the template constraint and library targeting guidance. Every sentence earns its place. It could be slightly more compact, but the structure is clear and scannable.

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?

The description covers the core purpose, the template constraint, and library targeting. However, with 7 parameters and 0% schema coverage, it leaves fields, creators, and collection_id semantics to inference. The output schema exists, so return values don't need explanation, but the parameter semantics gap makes this only minimally complete for an agent to call it correctly with complex metadata.

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 must compensate for the schema's lack of parameter documentation. The description explains the role of item_type (template determines accepted fields) and library_id/library_type (targeting another library), but it doesn't explain the semantics of fields, creators, or collection_id beyond what their names imply. The description adds some value but doesn't fully compensate for the 0% coverage.

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 specific verb ('Add') and resource ('an item') with a clear qualifier ('from manual, CSL-like, or previously parsed metadata'). It distinguishes itself from sibling tools like add_paper_by_doi or add_book_by_isbn by focusing on metadata-based creation rather than identifier-based lookup. However, it doesn't explicitly name a sibling alternative, so differentiation is implied rather than stated.

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 gives clear context for when to use this tool: when you have metadata in manual, CSL-like, or previously parsed form. It also provides explicit guidance on library targeting ('Pass both library_id and library_type to target another library; omit both to use the configured default'). It doesn't explicitly say when NOT to use it (e.g., when you have a DOI/ISBN/arXiv ID, use the sibling tools), but the context is clear enough for an agent to route correctly.

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