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

Annotations already disclose destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the description does not need to repeat these. The description adds minimal behavioral context beyond the kubectl analogy; it does not explain side effects or requirements. This is adequate given the annotations, but not especially rich.

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 short sentences that are front-loaded with the core action and immediately provide a useful analogy. Every word contributes; there is no redundancy or filler.

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?

Given the rich input schema (100% parameter coverage) and annotations (destructiveHint, readOnlyHint), the description is succinct but sufficient. The analogy to `kubectl patch` provides practical context for users familiar with Kubernetes tooling. It does not explain all nuances (e.g., patch types), but these are covered in the schema, and an output schema exists.

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 input schema covers 100% of parameters with descriptions, so the baseline is 3. The description itself adds no parameter-level details, but this is acceptable because the schema fully documents each parameter (e.g., patchType valid values, namespace default).

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's function: 'Patches a Kubernetes resource.' The verb 'patch' is specific and distinguishes it from sibling tools like apply_k8s_manifest, delete_k8s_resource, and get_k8s_resource. It also adds the apt comparison to `kubectl patch`, reinforcing the operation type.

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 usage via the analogy to `kubectl patch`, suggesting it's for partial updates to existing resources. However, it does not explicitly state when to use this tool over apply_k8s_manifest or other alternatives, nor does it provide exclusions. The guidance is implicit rather than explicit.

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