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

Annotations declare a non-readonly, non-idempotent, non-destructive mutation; the description is consistent with that and adds genuine context: the cluster is resumed with preserved configuration and storage, and unsupported providers fail the capability check rather than partially acting. It does not explain the non-idempotent implication (e.g., behavior if the cluster is already running).

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?

Two sentences, purpose first, constraint second, with no filler. The provider-support clause is dense but earns its place by preventing a guaranteed-to-fail call.

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?

No output schema exists, and the description covers the outcome (resume with preserved config/storage) and the provider gate, which is enough to call it correctly. Prerequisites such as required permissions and the already-running case are unaddressed, leaving a small gap for a state-changing lifecycle action.

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% and both parameters are optional-or-selected via the schema's own descriptions, so the schema already carries the parameter semantics. The description adds no selector precedence or format detail beyond it, which is the expected baseline when the schema does the heavy lifting.

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 ('Start a stopped managed Kubernetes cluster') and adds scope via 'through the provider' and 'managed', which separates it from generic lifecycle verbs. It does not name the sibling start_cluster / stop_managed_cluster to disambiguate managed vs unmanaged, so differentiation is implied rather than explicit.

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 gives a real precondition ('Currently supported by AKS only; other managed providers fail closed'), which tells the agent when the call will succeed. It never states when to prefer this over start_cluster or what to do when the provider is unsupported, so usage is implied rather than guided.

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