k8s_exec_pod

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

With no annotations, the description carries full burden but provides minimal behavioral insight. It states the action but doesn't disclose critical traits: whether this is a read-only or destructive operation (e.g., commands like 'rm' could delete files), authentication needs, rate limits, output format (stdout/stderr), or error handling. This is inadequate for a tool that executes arbitrary commands in a container.

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 a single, efficient sentence with zero waste—it directly states the tool's purpose without fluff. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 the tool's complexity (executing commands in a Kubernetes pod, which can be destructive) and lack of annotations or output schema, the description is incomplete. It fails to address safety, permissions, or result handling, leaving significant gaps for an AI agent to use it correctly in a production environment.

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 the schema fully documents all parameters (name, namespace, container, command). The description adds no additional meaning beyond the schema's parameter descriptions, such as examples for namespace defaults or command syntax nuances. Baseline 3 is appropriate when schema does the heavy lifting.

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 ('Execute a command') and target ('in a pod container'), which is specific and unambiguous. It distinguishes from siblings like k8s_get_pod_logs (read logs) or k8s_describe_pod (inspect), but doesn't explicitly contrast with them, so it's not a perfect 5.

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 is provided. It doesn't mention prerequisites (e.g., pod must be running), nor does it differentiate from similar operations like shell access or debugging tools. The agent must infer usage from the name and context alone.

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