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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds useful context by specifying that both client and server versions are retrieved and by comparing it to `kubectl version`, giving the agent a clear mental model of behavior beyond the annotations. No contradictions.

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?

The description is two concise sentences, with the action front-loaded. It provides no redundant information and every word adds value. The analogy to `kubectl version` is a useful explanatory touch without bloating the text.

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 simple one-parameter getter with an output schema, the description is complete. It clearly states what is retrieved and for which resource, while the schema handles the parameter format and the output schema covers return values. No additional context is necessary.

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 schema description covers 100% of the parameter, including the required format for `parent`. The tool description itself does not add parameter-specific details, but the schema already provides full semantics. With high schema coverage, a baseline score of 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?

The description clearly states the tool retrieves Kubernetes client and server versions for a cluster, using the specific verb 'retrieves' and a clear resource (versions). The similarity to `kubectl version` reinforces its purpose and distinguishes it from siblings like get_cluster or get_k8s_resource, which focus on other aspects.

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 provides clear context: it is used to get Kubernetes version information for a given cluster, analogous to `kubectl version`. While it doesn't explicitly name alternatives or state when not to use it, the narrow scope makes its use case unambiguous. The absence of exclusions is acceptable for a simple read-only getter.

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