merge_clusters

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

Discloses the destructive deletion of source cluster and mentions delegation to a registry method, but lacks details on reversibility or failure scenarios. No annotations to supplement.

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?

Two sentences: first provides high-level function, second implementation detail. Efficient but second sentence may be unnecessary for an agent.

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?

Simple tool with two parameters; output schema exists so return not needed. Adequate but could mention preconditions like cluster existence.

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 has 100% coverage; description merely restates slug roles without adding context beyond what schema provides.

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?

Clearly states the action: merge all papers from one cluster into another and delete the source. Distinct from sibling tools like split_cluster or apply_cluster_rebind.

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?

Implicitly describes when to use (to combine clusters), but lacks explicit guidance on when to use over alternatives like collect_to_cluster or propose_cluster_rebind.

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