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

Annotations only declare readOnlyHint=false, idempotentHint=false, destructiveHint=false. The description goes further by specifying exactly what is mutated (Cilium network identity allocated/flipped, overlay network mode stamped) and what is preserved (existing pod and service ranges), plus that convergence is asynchronous via existing jobs. It does not discuss failure modes or reversibility, so a 4 rather than 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?

Three sentences, front-loaded with the core action, then the triggering condition, then the qualification constraints. Every clause carries information (what, when, eligibility) with no filler.

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 mutation tool with no output schema, the description covers purpose, trigger, what changes, what is preserved, eligibility, and async convergence. It omits failure/reversibility behavior, which would round it out, but nothing required to call it correctly is missing.

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 100%, so cluster_id and site_public_ip are already documented. The description reinforces that cluster_id targets an existing cluster and that site_public_ip is proxmox-only, but adds no format or syntax details beyond the schema. Baseline 3 is appropriate.

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+resource ('make an EXISTING cluster mesh-capable in place, without rebuilding it') and explicitly distinguishes itself from rebuilding via create_cluster_mesh or joining via join_cluster_to_mesh. The 'in place, without rebuilding' qualifier lets an agent separate it from the mesh-creation siblings.

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?

Gives an explicit trigger ('Use this when check_cluster_mesh_readiness reports a remediable identity or network-mode failure'), names the upstream sibling that gates it, and lists eligibility constraints (upcloud/proxmox only, cluster online, proxmox needs site_public_ip). This is a clear when-to-use with exclusions.

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