consolidate_clusters

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

With no annotations, the description carries the full burden and does a lot: it discloses that nothing changes until a cluster is ripe, that each call nevertheless clusters every active record, and it enumerates return fields. It omits auth/permission needs, cost, or idempotency behavior, keeping it short of a 5.

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 trigger mechanism is front-loaded ('Cluster-TRIGGERED consolidation') and the description is dense but purposeful, with each sentence adding mechanism or rationale. It is slightly long but not padded.

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 single-parameter tool with no output schema, the description covers purpose, trigger semantics, non-obvious behavior, and return fields, which is enough to call it correctly. The main gap is the lack of explicit routing guidance versus the sibling `consolidate`.

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 the single `threshold` parameter has no schema description, so the description is the only source of meaning. It explains the trigger role of `threshold` ('grown past `threshold` members'), partially compensating, but says nothing about the default of 15 or the valid range.

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 gives a specific verb and resource ('consolidate a semantic cluster') and immediately scopes it against the global alternative ('not a global blanket'), which separates it from the sibling `consolidate`. It is clear and differentiated, though it never names the counterpart tool directly.

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?

It states the trigger condition ('only once it has grown past `threshold` members') and the rationale (avoid premature consolidation of sparse topics), which implies when to use it. However, it never explicitly says when to prefer this over the sibling `consolidate`, leaving the selection to inference.

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