get_k8s_default_version

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

The description adds context beyond the readOnlyHint annotation by explaining the tool's behavioral link to create_k8s_cluster and the k8s_version parameter omission case. It consistently supports the read-only nature indicated by the annotation without contradiction.

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 with zero waste. The first front-loads the primary action, and the second provides essential relational context about the create flow.

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 zero-parameter read-only lookup with no output schema, the description is complete: it defines what it returns, its relevance to new clusters and node pools, and how it fits into the cluster creation workflow. There is nothing more an agent would need to know.

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?

The tool has zero parameters, so the description has no parameter semantics to clarify. The baseline of 4 applies as there's nothing for the description to compensate for, and it appropriately focuses on what the tool returns.

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?

The description clearly states the tool retrieves 'the current default Kubernetes version used by new clusters and node pools in I IONOS CLOUD', which is specific about verb, resource, and scope. It also differentiates from sibling tools by noting the version is what create_k8s_cluster uses when k8s_version is omitted.

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?

The description implies when to use this tool by explaining its role in the cluster creation flow, letting agents understand it's for querying the default rather than specific versions. It doesn't explicitly contrast with list_k8s_versions, but the practical context given is nearly complete.

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