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

Annotations only cover readOnly/idempotent/destructive hints; the description goes well beyond them by disclosing the two-step design, that the call returns import_command, that the agent must be run against the cluster's kubeconfig, that the cluster shows 'offline' until check-in, and that existing names are refused rather than reconfigured. These details materially affect how an agent plans the operation.

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?

Purpose and the key differentiator are front-loaded, and almost every sentence conveys actionable information. Minor redundancy in 'any distribution, any provider, anywhere' followed by a provider list, but overall tight for the behavior it needs to convey.

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?

With no output schema, the description compensates by describing the return value (import_command) and the post-call cluster state. It also covers prerequisites and the sequencing to connect_gitops_repository, leaving nothing an agent needs to invoke this correctly unstated.

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% with only two fully documented parameters, so the schema already carries the parameter burden. The description reiterates the name-uniqueness rule ('a name that already exists is refused rather than reconfigured') but adds no new syntax or format detail, making the baseline 3 correct.

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 ('Import an EXISTING Kubernetes cluster into Ankra') and explicitly distinguishes itself from the create_*_cluster / create_managed_cluster siblings that provision new infrastructure. An agent can select it correctly without opening any schema.

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 explicit routing cues — 'Use this one whenever the user says import, onboard, connect, add, or bring in a cluster they already have' — plus a named follow-up alternative (connect_gitops_repository) for GitOps, and states what it is not for.

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