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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds real consequence detail: the cluster ceases to be a peer, remaining members' peer lists are re-rendered, and cross-cluster Services backed only by that cluster stop resolving. That downstream impact is not derivable from the annotations or schema.

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?

Three tight sentences: identity, consequence, then usage. The consequence sentence is front-loaded before the "use when" guidance, and nothing is redundant or 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 two-parameter destructive operation with annotations covering the safety profile and no output schema to explain, the description supplies what remains: the exact blast radius (peer lists re-rendered, dependent Services break). An agent has enough to call it correctly and warn appropriately.

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 100% with two well-documented UUID parameters, so the schema carries the parameter burden. The description adds no format, constraint, or ordering detail beyond what the schema provides, which is a baseline 3.

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?

States a specific verb and resource ("Remove one cluster from a mesh") and the scope word "one" implicitly distinguishes it from delete_cluster_mesh and join_cluster_to_mesh without requiring the schema. An agent can tell what it does and what it does not do at a glance.

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?

"Use when retiring a cluster or undoing a join" gives explicit triggering conditions, and the join reference points the agent at the inverse operation. It stops short of naming a sibling tool or stating a when-not case (e.g. use delete_cluster_mesh to dismantle the whole mesh), so it is clear context without full routing.

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