get_k8s_nodepool

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

Annotations already provide readOnlyHint=true, so no contradiction. The description adds valuable context about how the returned data relates to update operations (list replacement) and availableUpgradeVersions, which is beyond the annotation and helps the agent understand the data's implications.

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 concise sentences, each with purpose: listing details, providing crucial usage warning, and noting a specific output field. No redundant text; perfectly front-loaded.

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 read-only get operation with full schema coverage and no output schema, the description is highly complete. It covers what the tool returns, why it's useful (pre-update check), and mentions upgrade paths, leaving no major gaps.

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 description coverage is 100%, so parameters are fully documented. The description does not add extra parameter-level meaning beyond what's in the schema, but it does mention a returned field (availableUpgradeVersions) that clarifies the output. 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?

Clearly states it gets details of a specific Kubernetes node pool and enumerates the specific fields (node count, hardware, autoscaling bounds, LANs, labels, annotations). Distinguishes from the many sibling get_* tools by naming the resource and its scope.

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 instructs to read this before calling update_k8s_nodepool for certain fields, and explains that those fields replace entire lists. Also mentions availableUpgradeVersions for version migration context, giving clear when-to-use guidance.

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