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

Annotations already declare readOnlyHint=true, and the description reinforces this ("without changing anything", "Read-only"), so credit is for the added detail: it discloses the specific validation passes performed and that results come back as errors and warnings per resource. It stops short of describing severity handling or limits, so not a 5.

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?

Front-loaded with the core action, then the check list, then the sequencing and read-only cue. Efficient overall, though the first sentence is dense enough to require a second read.

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 a single fully documented required parameter and no output schema, the description still tells the agent what nothing else does: that it returns errors and warnings per resource and that it is a non-mutating pre-flight step. Nothing needed to invoke it correctly is missing.

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% and the schema description is rich (base64 encoding, 2 MiB cap, accepted inline blocks, from_file refused). The description adds nothing beyond the parameter name, so the 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?

States a specific verb (validate) and resource (ImportCluster YAML), then enumerates what is checked: structural checks, chart catalog, dependency/variable references, live cluster state. This distinguishes it from the many apply_*/create_* siblings, and it explicitly names apply_cluster_manifest as its counterpart.

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 a clear sequencing rule: "Run this before apply_cluster_manifest." That names the alternative and the condition that selects this tool. It does not state any when-not condition, but for a pre-flight validator the guidance is strong.

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