zotero_add_from_file

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

No annotations provided, but the description thoroughly covers behavioral aspects: file type rejection, DOI extraction and fallback, metadata enrichment, optional overrides, cloud quota limit, and need to run zotero_update_search_database after.

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 detailed and well-structured, with key information front-loaded. While it covers all necessary aspects, it is somewhat long and could be slightly more concise without losing value.

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 (5 parameters, no schema descriptions, output schema exists), the description provides comprehensive context: use case, prerequisites, limitations, side effects, and recommended post-step. Output schema exists, so return values are not needed.

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 0%, but the description explains file_path (absolute path), title (override), collections (8-char keys/names), and tags. However, it does not explain the item_type parameter, which is left with default 'document' but unclear.

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 a local .pdf or .epub file, explains metadata enrichment via DOI extraction and fallback, and distinguishes from sibling tools like zotero_add_by_doi and zotero_add_by_url.

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?

Explicitly says to use when the user has a file on disk but no DOI/URL, and directs to alternative tools for DOI or URL cases. Also notes conditions like writable library, file size limits, and post-step requirement.

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