search_pubmed_to_collection

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

The description states the key side effect ('add results'), which signals a write to Zotero, and no annotations are present. It does not disclose details like collection creation, duplicate handling, or rate limits, but the schema covers creation behavior via create_collection.

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, efficient sentence with no filler and front-loads the main action. It is concise but slightly underspecified for usage context.

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 moderate-complexity tool with no output schema and no annotations, the description plus full parameter schema is mostly sufficient to call it. It lacks sibling differentiation and behavioral caveats, but the core operation is adequately conveyed.

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?

Input schema covers 100% of parameters with descriptions, so the description needs to add little. The description aligns with query and collection_name, but adds no semantics beyond the schema.

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 uses a specific verb ('search') and resource ('PubMed') and specifies the destination ('a Zotero collection'), making the operation clear. It does not explicitly distinguish from sibling tools like search_arxiv_to_collection or search_multi_source_to_collection, so it stops short of full differentiation.

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 implied use case is evident: when a user wants PubMed results added to a Zotero collection. However, the description provides no explicit when-to-use guidance, no exclusions, and no mention of alternative sibling tools for Arxiv or multi-source searches.

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