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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, yet the description still adds real behavioral context: a per-call price ($0.003 USDC via x402 on Solana), an alternate HTTPS endpoint, and the response shape ('per-resource findings with a 0-100 score'). It does not say whether the call fails or returns findings on malformed YAML, which is the remaining gap.

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 purpose is correctly front-loaded in the first clause, but the middle of the description is a long comma-separated enumeration of a dozen-plus check categories that is dense and hard to scan, and much of it could be trimmed without losing selectability. The pricing and endpoint sentences do earn their 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?

For a single-input read-only linter with no output schema, the description covers what is checked, what comes back (per-resource scores), the cost of the call, and an alternate transport — which is enough for an agent to invoke it correctly. Only error/failure behavior on invalid YAML is left unstated.

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?

There is a single required parameter with 100% schema description coverage, so the baseline would be 3. The description earns one step above baseline by clarifying accepted input breadth — multi-document YAML and List kinds — which is meaning the schema's 'separated by ---' only partially conveys.

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 opens with a precise verb+resource: 'Security and reliability audit of Kubernetes YAML', and enumerates the exact classes of findings (privileged containers, RBAC wildcards, committed Secret data), so an agent knows exactly what it does. It does not differentiate itself from the closely related siblings in this catalog (dockerfile_lint, gha_workflow_lint, container_check, schema_validate), which is what keeps it from a 5.

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 only implied: the schema's '---' separator convention and the description's 'multi-document, List kinds' note tell the agent it should feed YAML manifests, and the HTTPS/x402 line implies a paid alternative endpoint. There is no explicit statement of when to pick this over container_check or schema_validate, and no prerequisites or exclusions are given.

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