k8s_run_pod

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

No annotations provided. Description mentions it creates and runs a pod, and hints at restart behavior. However, it does not disclose persistence, cleanup, idempotency, or permissions needed. Minimal extra behavioral context beyond purpose.

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?

Three short sentences with front-loaded purpose, followed by usage context and specific tip. No redundant text; every sentence earns its place.

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 8 parameters, 0% schema coverage, no annotations, and no output schema, the description is too brief. It does not explain required 'context', optional parameters, or what happens after pod creation. Significant gaps for an average-complexity tool.

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 has 8 parameters with 0% description coverage. Description only adds meaning to 'image' (container image) and 'restart' (hint for one-shot). No explanation for 'context', 'namespace', 'env', 'labels', 'command'. Insufficient for a tool with many params.

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 'Create and run a pod with the specified container image', specifying the verb and resource. It distinguishes from sibling tools like k8s_create_resource (general resource creation) and k8s_get_pod_logs (logs).

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?

Provides context: 'Useful for running one-off tasks, debugging, or testing.' Advises setting restart='Never' for one-shot jobs. Lacks explicit exclusions or alternatives, but gives clear usage scenarios.

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