exec_in_pod

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

With no annotations, the description carries full burden. It discloses the key behavioral trait that command is split with shlex and shell metacharacters are not interpreted. However, it omits details like whether it connects to a running container or output format (though output schema exists). The disclosed trait is valuable and goes beyond a generic 'execute command'.

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?

Two sentences, no fluff. Every word adds value: the first states the action, the second clarifies a critical behavioral detail. No unnecessary information.

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 5 parameters, no schema descriptions, and no annotations, the description is far too brief. It lacks parameter explanations, usage context, and error/edge case behavior. The presence of an output schema does not compensate for the missing parameter semantics.

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 0%, so the description must add meaning beyond the schema. It does not mention any parameter names, purpose, or defaults. For 5 parameters including 'name' and 'command', the description provides no explanation of what each parameter does.

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 tool's action: 'Execute a command inside a pod via oc exec.' It also adds specific detail about shlex splitting and shell metacharacters not being interpreted. This distinguishes it from sibling tools like 'run_oc_command' or pod management tools.

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 provides no guidance on when to use this tool versus alternatives (e.g., run_oc_command) or any prerequisites (e.g., pod must be running). The shlex note is behavioral, not usage direction.

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