collect_to_cluster

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

No annotations provided, so description bears full burden. While it describes routing logic, it omits critical behaviors: effect of boolean flags (e.g., dry_run, skip_verify), whether actions are synchronous, side effects on cluster, or authentication needs.

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?

One sentence, front-loaded with 'Unified ingest', no redundant words, and efficiently conveys the routing concept.

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 5 parameters and a routing function, the description is too brief. Lacks explanation of boolean flags, output structure (though output schema exists), and edge cases, leaving significant gaps for an agent.

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 0% and description adds no parameter meanings. It only mentions source and cluster_slug implicitly via routing, but no explanation of skip_verify, no_zotero, or dry_run.

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 'Unified ingest' and explains auto-routing based on source shape (DOI/arXiv, folder, URL), effectively distinguishing it from siblings like add_paper and import_folder_tool.

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 usage when the source type is unknown or varied ('auto-routes'), but lacks explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives beyond the routing examples.

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