split_cluster

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

No annotations exist, so the description must fully disclose behavior. It lacks details on side effects (e.g., whether source cluster is modified), authorization needs, or the role of the 'query' parameter. The phrase 'title keyword overlap' is ambiguous without further explanation.

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 concise sentence that front-loads the action. It is not verbose, but could add essential detail without sacrificing brevity.

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 the complexity of cluster operations and the presence of an output schema (not shown), the description should explain what the tool returns (e.g., new cluster details). It currently lacks completeness regarding post-invocation state and results.

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 zero parameter descriptions (0% coverage). The description only hints at 'title keyword overlap' but does not clarify the meaning of 'query' or how it interacts with the other parameters. The agent would need to infer parameter roles from the name alone.

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 the action (split), the resource (source cluster into new cluster), and the method (based on title keyword overlap). It distinguishes from related siblings like merge_clusters and suggest_cluster_split, but could be more precise about the exact operation.

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?

No guidance on when to use this tool versus alternatives like suggest_cluster_split or manual splitting. No prerequisites or conditions mentioned, leaving the agent without context for proper invocation.

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