enable_cluster_ha

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

Discloses all key behaviors: money spent, irreversibility, idempotence, required scope, and confirm requirement. No annotations provided, so description fully carries the burden.

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?

Four sentences plus a phrase, no fluff. Information is front-loaded with purpose, then requirements and caveats. Every sentence adds value.

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 tool complexity and no output schema, description covers all necessary aspects: action, prerequisites, cost, irreversibility, and confirmation needed. Complete for agent usage.

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% but description adds value: explains confirm is needed only after user approval and that service_id comes from list_services. Goes beyond schema.

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 it enables HA control plane on a managed Kubernetes cluster, with specific effect (multi-zone API server/etcd). Distinguishes from siblings by being a unique enabling action.

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?

Explicitly says it's add-only, irreversible, and requires user approval due to cost. Specifies when to use (after user approves) and where to get service_id. Provides idempotency info.

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