k8s_label_resource

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

Without annotations, the description must disclose behaviors beyond the name. It mentions add/update but omits critical details: whether labels are merged or replaced, the impact of the 'overwrite' parameter, if the resource must exist, and whether removing labels is possible. The description adds minimal value over the tool name.

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 sentences long and front-loaded with the core purpose. It wastes no words, but could be more informative within the same length (e.g., clarifying the overwrite parameter's effect).

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 6 parameters, no output schema, and no annotations, the description is incomplete. It does not explain label merge behavior, the role of 'overwrite', or how to remove labels. An agent cannot safely invoke this tool based on the description alone.

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%. The description only mentions labels as key-value pairs but does not explain any of the 6 parameters (context, resource_type, name, namespace, labels, overwrite). Their purpose and constraints are entirely absent, leaving the agent to guess roles and valid inputs.

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 action ('Add or update labels') and the target ('a Kubernetes resource'), distinguishing it from siblings like k8s_annotate_resource (annotations) and k8s_patch_resource (generic updates). The definition of labels as key-value pairs adds context.

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 provides clear context (managing labels on resources) but offers no explicit guidance on when to use this tool versus alternatives like k8s_annotate_resource or k8s_patch_resource. No exclusions or prerequisites are stated.

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