exec_command

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

The description discloses the return behavior (stdout/stderr/exit code), which is useful. However, with no annotations, it fails to disclose potential side effects of running arbitrary shell commands (e.g., modifying files, installing packages, or changing container state), and provides no safety context.

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?

A single sentence that delivers the core function and return values with no filler. It is front-loaded with the action and resource, making it efficient for an agent to parse.

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 tool that executes commands, the description omits essential context: what 'name' refers to, how the container is selected, whether the pod must be running, and what side effects may occur. The lack of any caveat or usage note makes it incomplete for safe autonomous invocation.

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 0% parameter description coverage, so the description must define the parameters. It implies 'command' is the shell command, but 'name' is left ambiguous (pod name? container name? a composite identifier?). The description does not clarify how 'name' maps to the target container.

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 states a specific verb ('Run'), a resource ('a pod's container'), and the key return values ('stdout/stderr/exit code'). This clearly distinguishes it from sibling tools like get_logs or read_file, which inspect without executing arbitrary commands.

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 implies usage: when you need to execute a shell command inside a container. However, it gives no explicit guidance on when to prefer this over alternatives like get_logs or list_files, and does not mention exclusion criteria such as read-only operations or file inspection.

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