sync_zotero_library

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

Since no annotations are provided, the description carries full burden for behavioral disclosure. It correctly indicates the default incremental behavior and the full sync option. However, it lacks details on potential side effects (e.g., overwriting existing metadata, error states, or rate limits). The description is adequate but not comprehensive.

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 concise and well-structured: it opens with the purpose, then explains default behavior, required environment variables, and the parameter. Every sentence earns its place with no redundancy or fluff.

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 tool's simplicity (one boolean parameter) and the presence of an output schema, the description covers the basic functionality. However, it omits details about return values, error handling, and the extent of the sync (e.g., collections, attachments). It is minimally complete but leaves gaps for a production tool.

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, the description adds crucial meaning for the sole parameter 'full'. It explains the default behavior and the effect of setting it to True, which goes beyond the schema's structural definition. This is clear and helpful.

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 verb ('Sync') and resource ('Zotero library into Metis literature_metadata'), making the tool's purpose unambiguous. It distinguishes itself from sibling tools (e.g., import_bibtex_library, scan_literature) by specifying the exact integration with Zotero.

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 explains default behavior (incremental sync) and the option to force full sync via the 'full' parameter. It also lists required environment variables (ZOTERO_API_KEY, ZOTERO_USER_ID), providing context for use. However, it does not specify when to avoid this tool or mention alternatives among siblings.

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