k8s_annotate_resource

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

With no annotations provided, the description carries full burden for behavioral disclosure. It does not indicate whether the tool is read-only or mutating, whether it requires special permissions, or how 'update' works (merge vs replace). The schema includes an 'overwrite' parameter defaulting to false, but the description does not mention this, leaving behavior ambiguous.

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—first states the action, second adds context about annotations. No redundant or extraneous wording. However, the brevity sacrifices completeness, so it is not an optimal trade-off.

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 no output schema, 0% schema coverage, and 6 parameters (4 required), the description is far too minimal. It fails to specify how to use the tool, what the annotations object expects, the effect of overwrite, or the role of namespace. An AI agent cannot reliably invoke this tool based solely on the description.

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 schema has 0% description coverage for all 6 parameters. The description does not explain any parameter (e.g., 'context', 'annotations', 'overwrite'). For a tool with 4 required parameters and a nested annotations object, this is severely lacking. The agent must rely solely on parameter names, which may be unclear.

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 annotations') and the target ('Kubernetes resource'). It also explains what annotations are for (non-identifying metadata). This distinguishes it from siblings like k8s_label_resource, which manages labels instead of annotations. However, it does not explicitly contrast with k8s_patch_resource, which could also modify annotations.

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?

No guidance on when to use this tool versus alternatives (e.g., k8s_patch_resource, k8s_label_resource). It does not mention prerequisites, appropriate contexts, or when to avoid using it. The description lacks any usage direction.

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