zotero_synthesize_annotations

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

With no annotations, the description carries full burden. It discloses the tool only gathers and groups material, does not call an LLM, and returns markdown grouped by paper. It also mentions caps (limit default 200) and optional filters, providing full behavioral transparency.

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 but not overly verbose. It is well-structured with clear sections for purpose, parameters, output, and usage. The example at the end is helpful but could be considered slightly extraneous. Overall, it earns its place.

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 3 optional parameters and presence of output schema, the description is complete. It explains the tool's function, scope, filtering, output format, and use case. No gaps are evident.

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 description coverage is 100%, so baseline is 3. The description adds meaningful context: collection_key effect on scope, tag accepting multiple formats, and limit default. This goes slightly beyond schema briefs, warranting a 4.

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 collects highlights, annotations, and notes across a scope into a structured digest, and explicitly distinguishes itself by stating it does NOT call an LLM. This differentiates it from sibling tools like zotero_get_annotations or zotero_get_notes.

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 advises using the tool before writing a thematic review to spot themes and contradictions. It explains when to use collection_key versus omitting it. However, it does not explicitly state when not to use it, though the context implies using other tools for raw data retrieval.

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