collect_to_cluster

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

No annotations are provided, so the description must disclose behavioral traits. It explains auto-routing behavior and mentions the dry_run parameter, but does not describe side effects, authorization needs, or potential destructiveness. The information is adequate but not comprehensive.

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?

A single well-structured sentence front-loads the core purpose ('Unified ingest') and efficiently details the routing logic with examples. No unnecessary words or repetitions.

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?

Given five parameters with no documentation and the complexity of an ingest operation, the description is insufficient. It does not cover how to use each parameter, expected output, or error cases. Although an output schema exists, the description lacks completeness for reliable agent invocation.

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 0%, so parameter descriptions are missing entirely. The description only indirectly clarifies the 'source' parameter by listing example source types (DOI, arXiv, folder, URL). Other parameters like skip_verify, no_zotero, dry_run are not explained, adding minimal value beyond parameter names.

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 it is a unified ingest tool that auto-routes based on source shape, and it distinguishes between siblings by naming specific delegated actions (add_paper, import_folder, URL file). The verb 'collect' is implicit in 'ingest'.

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 clearly implies when to use this tool (for DOI, arXiv, folder, URL inputs) and references alternative tools for specific use cases. However, it does not explicitly state when not to use it or provide exclusions, leaving some ambiguity.

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