generate_k8s_manifest

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

With no annotations at all, the description carries the full burden. It does add real behavioral detail beyond the schema — output is "linted" and "production-hardened" with non-root securityContext, probes, and resource bounds always applied — but it never says whether anything is written to disk or applied to a live cluster, whether generation is idempotent, or what the response looks like.

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?

One dense sentence, front-loaded with the action and resource, with zero filler. Every clause (manifest kinds, security hardening, probes, resource limits) contributes signal.

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?

For a 10-parameter generation tool with no annotations and no output schema, the description leaves the return contract undefined: does it return YAML text inline, multiple documents when `kind: "all"`, or file paths? It also omits whether any cluster interaction occurs. Parameter-level gaps are covered by the schema, but the output/behavioral side is thin.

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 description coverage is 100%, so all 10 parameters are already documented with defaults and an enum. The description's mention of the four manifest kinds and the hardening defaults loosely reinforces `kind` and `enable_security_context`, but adds no syntax or format meaning beyond the schema — baseline 3 applies.

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?

States a specific verb ("Generate") + resource ("Kubernetes YAML manifests") and enumerates the artifact types produced (Deployment, Service, HPA, PDB) plus the qualities baked in (securityContext, probes, requests/limits, linted). No sibling in the list produces manifests, so the tool's identity is unmistakable without opening the schema.

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?

There is no statement of when to call this versus alternatives, no prerequisites, and no note about what it is not (e.g., it does not apply to a cluster or edit existing manifests). An agent must infer usage entirely from the verb.

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