kubectl_patch

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

Annotations already indicate destructiveHint=true, so the description's claim of 'updating' is consistent. However, it adds minimal extra transparency beyond listing patch methods—no mention of idempotency, reversibility, or required permissions, which would be valuable for a mutation tool.

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 a single, front-loaded sentence that efficiently conveys the action and method. It could be slightly improved with a brief usage hint but is not overly verbose.

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 tool's complexity (8 parameters, three patch types, no output schema), the description is too minimal. It does not explain return values, error handling, or how to structure patches. Sibling differentiation is absent, leaving the agent without enough context to use the tool effectively.

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?

Input schema has 100% description coverage and all parameters are described. The description does not add any further meaning beyond the schema; for example, it does not clarify the difference between patchData and patchFile or provide usage examples.

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 purpose: updating fields of a Kubernetes resource using specific patch methods (strategic, merge, JSON). It distinguishes from siblings like kubectl_apply (declarative create/update) and kubectl_create (create new resources).

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 fails to provide any guidance on when to use this tool versus alternatives such as kubectl_apply or kubectl_create. No context is given regarding prerequisites, distinctions between patch types, or scenarios where patching is preferred.

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