What does this Kubernetes field do?

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world). The description adds genuine behavioral context beyond them: content is sourced from the versioned API and defaults to the newest version. It stops short of stating failure modes (e.g., unknown kind or unresolvable path).

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 purpose, then parameter mechanics, all in a single dense sentence-group with zero filler. Examples are embedded inline rather than padding 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?

With an output schema present, return values need no explanation, and the description covers addressing modes, defaults, and fallbacks adequately for a read-only lookup tool. It is only marginally incomplete in not hinting at unsupported kinds or lookup failure behavior.

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 only 25% (just `kind`), but the description compensates thoroughly: it defines `field` as a dotted path with a concrete example, explains omitting it for top-level, defines `search` as word-based with an example query, and notes `kubernetes_version` defaults to newest. All four parameters gain meaning beyond the schema.

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+resource: it explains what a field of a Kubernetes kind 'means and accepts' from the versioned API. The scope (per-field documentation lookup, with dotted-path addressing) is unmistakably distinct from the sibling manifest-checking and API-version tools.

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 clear in-tool routing: use `field` for a dotted path, 'omit it for the kind's top level', and use `search` for word-based discovery with a worked example. It does not, however, state when to reach for this tool over api_versions or check_manifests, nor any preconditions.

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