zotero_synthesize_annotations

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

With no annotations provided, the description fully carries the transparency burden. It discloses that the tool does NOT call an LLM, only gathers and groups material, and that synthesis is left to the agent. It also explains scoping behavior (whole library vs. collection, cap by limit) and output details, leaving no major behavioral surprises.

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 moderately long but every sentence adds value. It front-loads the main purpose, then covers the no-LLM aspect, parameter behaviors, output format, and a concrete usage example. No fluff or repetition.

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?

The description is complete for a tool with 4 optional parameters, an output schema (present), and a wide sibling set. It explains output structures for both markdown and json formats, gives an example call, and provides enough context for correct invocation and interpretation of results.

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?

Although schema coverage is 100%, the description enriches each parameter beyond the schema. For example, it clarifies that collection_key filters by resolved paper membership and that omitting it scans the whole active library, and it explains the markdown output structure for format. This goes well beyond the schema's terse descriptions.

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's function: 'Collect every highlight, annotation comment, and child note across a scope and organize them into a structured, per-paper digest.' It explicitly distinguishes itself from LLM-based synthesis and from sibling tools like zotero_get_annotations by emphasizing aggregation and grouping rather than raw retrieval.

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 gives an explicit use case: 'Use this before writing a thematic review so you can spot themes and contradictions across sources.' It explains when collection_key and tag filters are appropriate, but it does not explicitly name alternative tools for when this one is not suitable, so it gets a 4 rather than a 5.

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