sync_zotero_library

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

Describes sync behavior (incremental vs full) and prerequisites (env vars). With no annotations, it carries the burden but lacks disclosure on idempotency, error handling, or potential data duplication.

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?

Four well-structured sentences front-load the purpose and behavior. No unnecessary words 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?

Covers core behavior, parameter, and prerequisites. Lacks details on return values (but output schema exists) and update/insert semantics. Adequate for a simple sync 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 'full' is clearly described: 'If True, re-sync all items regardless of last sync state.' This adds value beyond the schema's default and type info.

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?

Clearly states 'Sync the Zotero library into Metis literature_metadata', specifying action and target. Though no explicit sibling differentiation, it is distinct from other tools.

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?

Explains default incremental sync and optional full re-sync via the 'full' parameter. Mentions required environment variables (ZOTERO_API_KEY, ZOTERO_USER_ID). Does not include exclusions or when not to use.

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