Add Item From Metadata

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

The description adds useful behavioral context about Zotero item template validation ('preventing invalid cross-type metadata'), which is beyond the annotations. However, it does not disclose other behaviors like permission requirements, duplicate handling, or what happens on invalid input. Annotations are not contradicted, but the additional transparency is limited.

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 two sentences, front-loaded with the primary purpose and a concise second sentence explaining field validation. Every sentence earns its place without verbosity or redundancy.

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 and one behavioral aspect (template-based validation), and an output schema exists so return values need not be described. However, it lacks parameter semantics and explicit usage guidance, making it only partially complete for a tool with 5 parameters and 0% schema coverage.

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?

With 0% schema description coverage (no parameter descriptions), the description must compensate, but it only vaguely references 'fields' through the template validation note. It does not explain the semantics of 'title', 'creators', 'collection_id', or the structure of 'fields' and 'creators'. This is a significant gap for a 5-parameter tool.

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 tool adds an item from metadata ('manual, CSL-like, or previously parsed metadata'), which distinguishes it from identifier-based siblings like add_paper_by_doi. The verb 'Add' and resource 'item' are specific, though it does not explicitly name sibling alternatives, so it falls slightly short of a 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?

The description implies the tool is for when you have metadata rather than a DOI/ISBN/arXiv ID, as indicated by 'from manual, CSL-like, or previously parsed metadata.' However, it does not explicitly state when not to use it or name alternative tools, leaving usage guidance implied rather than explicit.

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