search_multi_source_to_collection

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

With no annotations provided, the description bears the full burden of behavioral disclosure, yet it only states the basic action. It does not reveal that the tool writes to the user's Zotero library, that it can add up to max_results_per_source items per source, or how duplicate results across sources are handled. The meaning of 'combine' and any side effects are left unstated.

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 a single well-ordered sentence with no filler: the verb 'Search' is front-loaded, and each phrase carries meaning (sources, outcome, destination). It is as compact as a correct description can be.

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?

With five parameters, no annotations, and no output schema, the description must carry substantial load but does not. It omits when to prefer this over single-source siblings, the write/side-effect profile on Zotero, and how combined results behave. An agent needs more than this one sentence to invoke the tool safely and correctly.

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 the schema already documents all five parameters and the baseline is 3. The description only echoes what the schema states ('multiple sources' maps to sources, 'Zotero collection' maps to collection_name) without adding deeper detail about formats, constraints, or parameter interactions.

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 states a specific verb ('Search'), names both concrete sources ('PubMed, arXiv'), and specifies the resulting action ('combine results in a Zotero collection'). It is clear and actionable, and the 'multiple sources' phrasing implicitly distinguishes it from single-source siblings like search_pubmed_to_collection, but that differentiation is not made explicit.

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 offers no guidance on when to use this tool versus the closely related single-source siblings search_pubmed_to_collection, search_arxiv_to_collection, or the general zotero_search. An agent must infer the selection criteria entirely from sibling names and the schema, with no stated conditions or exclusions.

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