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

Annotations already declare readOnlyHint=true, so the trailing "Read-only." is redundant. However, "For Scaleway Kapsule the listing reconciles against the provider first" is genuine behavioral context beyond annotations: it warns of a provider-side refresh and likely latency for that provider.

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?

One front-loaded sentence delivers the resource, the returned fields, and the provider scope before the qualifiers. The trailing "Read-only." duplicates the readOnlyHint annotation and is the one phrase that doesn't earn its place.

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 compensates by enumerating the fields returned, which is the main thing an agent needs. It stops short of describing behavior when neither cluster_id nor cluster_name is supplied (all clusters?) and says nothing about pagination or ordering.

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 covers both parameters at 100% with cluster_id and cluster_name well documented ("Optional when a cluster is selected"). The description adds nothing about selecting, precedence between id and name, or listing behaviour across all clusters, so 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?

Names a specific verb and resource (list node pools of a managed Kubernetes cluster) and enumerates exactly which attributes come back (size, count, zone, autoscaling bounds, labels, taints, provider status). The provider list (DOKS, UKS, GKE, AKS, EKS, OVH MKS, Kapsule, Ankra) scopes it against the generic list_node_groups sibling.

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?

Usage is implied only: it is a read-only listing of managed-cluster node pools, with the reconciliation note hinting at when you'd call it against Kapsule. It never states when to prefer it over siblings such as list_node_groups, get_cluster_details, or describe_resource, and gives no exclusions.

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