k8s_patch_resource

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

No annotations exist, so description bears full burden. States 'update specific fields' and 'strategic merge patch' implying mutation, but does not disclose idempotency, error behavior (e.g., fails if resource missing), or side effects. Lacks at least 3 behavioral traits given absence of annotations.

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?

Two concise sentences: first states purpose and patch type, second lists supported resource types. No unnecessary words, but could be more structured (e.g., bullet points for types).

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?

No output schema and 5 parameters with 0% coverage. Description omits crucial details like patch format, namespace optionality, context role, and return behavior. Incomplete for effective usage.

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 0%, description adds no parameter-level meaning beyond the schema. Does not explain format of 'patch' object, resource_type spelling, or purpose of context/namespace. Minimal added value.

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?

Description clearly states the tool updates specific fields of a resource using a strategic merge patch, listing supported resource types (pod, deployment, etc.), which distinguishes it from sibling tools like k8s_update_resources or k8s_apply_resource.

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?

Implied usage for patching specific fields, but no explicit guidance on when to use this over alternatives like k8s_update_resources (full update) or k8s_apply_resource (apply configuration). Lacks when-not-to-use or prerequisite conditions.

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