Zotero Synthesize Annotations

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

With no annotations, the description carries full burden and handles it well: it states the tool does NOT call an LLM, only gathers and groups raw material, caps scans by limit, and describes the markdown vs json output behavior plus the summary count line. This goes well beyond the structured schema.

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 dense and front-loaded with purpose, then behavior, parameters, output, and usage. A few output details are repeated ('groups the digest by paper' and the later markdown-output sentence), so it is not maximally tight, but no sentence is filler.

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?

For a four-parameter, no-annotation tool with an output schema, this is complete: it explains scope resolution, filtering, limits, output formats and counts, and gives a concrete example call. An agent has what it needs to invoke correctly and know what to expect.

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?

Even though schema coverage is already 100%, the description adds meaning: collection_key is 8 characters and filters by resolved-paper membership, omitted means whole active library, tag accepts string/JSON list/list, limit caps scan tractability, and format differences are explained. This is exactly the added semantic value parameter descriptions should provide.

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 names a specific action and resource: 'collect every highlight, annotation comment, and child note' and 'organize them into a structured, per-paper digest.' It also clarifies what the tool is not (it does not call an LLM), which separates it from synthesis-like workflows and sibling retrieval 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?

It gives a clear use case: 'Use this before writing a thematic review so you can spot themes and contradictions across sources.' It does not explicitly name sibling tools like zotero_get_annotations or zotero_get_notes as alternatives, nor state when not to use this tool, so it misses 'when-not' guidance.

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