sync_zotero_local

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

With no annotations provided, the description fully bears the burden of disclosure. It explains that it reads a local file, imports into literature_metadata with library_source='zotero-local', and mentions that the same table is used by the Librarian and search_library. It also describes the default behavior for db_path. This provides good insight into expected behavior beyond a simple 'import' statement.

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, using only two paragraphs. The first sentence states the core purpose. The second explains the advantage over the sibling. Then the argument description is clear and structured. Every sentence adds value, and there is no 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?

Given that an output schema exists (not shown but referenced), the description adequately covers the input and the outcome (importing into literature_metadata). It mentions the database path search behavior and the destination table. It does not explicitly handle error cases like file not found, but the default path search provides reasonable robustness. Overall, it is fairly complete for a straightforward import 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?

The single parameter db_path has 0% schema description coverage, so the description must compensate fully. It does so by explaining the parameter is a path to zotero.sqlite, and if left empty, Metis searches common locations. This adds significant meaning beyond the schema's minimal 'Db Path' title and default value.

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 imports a local Zotero library by reading zotero.sqlite directly, without an API key. It explicitly distinguishes itself from the sibling sync_zotero_library by specifying it is the offline alternative. The verb 'import' and resource 'local Zotero library' are specific, and the output table is named.

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 explicitly says 'The offline alternative to sync_zotero_library' and highlights that it works with no API key and no network, providing clear when-to-use guidance. Although it does not list scenarios when not to use, the emphasis on offline use and comparison to the sibling tool provides adequate context for choosing between them.

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