arvan_kubectl

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

Annotations indicate readOnlyHint=false, destructiveHint=false, and idempotentHint=false. The description does not clarify that kubectl commands can be destructive or have side effects, leaving the agent unaware of potential risks. No additional behavioral context beyond the schema is given.

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 concise with a single sentence and includes a code example. While clear, it lacks structured details that could improve usability without adding bulk.

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 runs arbitrary kubectl commands, the description omits important context: no output schema, no error handling guidance, no permission requirements, and no examples beyond a basic case. This leaves significant gaps for an agent to use it effectively.

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?

The description provides no explanation for any of the four parameters, and schema coverage is 0%. The description fails to add meaning beyond the schema, leaving the agent without guidance on how to use kubeconfig, namespace, or args effectively.

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 runs an arbitrary kubectl command with a specific verb and resource. It distinguishes itself from sibling tools like arvan_k8s_apply, arvan_k8s_get, and arvan_k8s_delete by covering commands not handled by those specialized 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 implies usage for arbitrary kubectl commands not covered by specific siblings, but it does not explicitly define when to use this tool versus alternatives. No guidance on when not to use or prerequisites is provided.

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