search_arxiv_to_collection

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

With no annotations available, the description carries the full burden of disclosing behavior, but it only states the basic action. It does not mention side effects like creating a collection if it doesn't exist, any duplicate handling, behavior with max_results, or what happens on partial failure — important for a tool that writes to an external system.

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, front-loaded sentence with no filler or redundancy. It is concise and easy to parse, though it omits behavioral details that would make it more useful.

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 tool has four parameters, no output schema, and no annotations, yet the description only provides a high-level summary. It does not explain return behavior, side effects, default collection creation, or interaction with the Zotero library, so an agent would need to rely on the schema and guess about runtime behavior.

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 coverage is 100%, so the input schema already documents query, max_results, collection_name, and create_collection with helpful descriptions and defaults. The description adds no extra parameter meaning, but it does not need to since the schema is sufficient.

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 action ('Search arXiv') and a clear destination effect ('add results to a Zotero collection'), making the tool's purpose immediately identifiable. It also distinguishes itself from siblings like search_pubmed_to_collection by explicitly naming arXiv as the source.

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 implies the tool should be used when the agent needs to find arXiv papers and place them into a Zotero collection. However, it provides no explicit guidance about when not to use it or which sibling alternative to prefer, such as search_pubmed_to_collection or zotero_search.

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