vcluster_kubeconfig

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

With no annotations provided, the description carries the full burden, and it does well. It discloses that the kubeconfig is written to a private 0600 temporary file, returns the path rather than contents for security reasons, and notes that the caller owns and should delete the file.

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 well-structured and front-loaded with the core purpose, followed by usage context, behavioral notes, parameter details, and return type. Every sentence adds useful information without padding.

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 with five parameters and no annotations, this description is complete. It covers use case, behavior, file ownership, parameter semantics, and the return shape, leaving little ambiguity for an agent deciding whether and how to invoke it.

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%, but the Args section fully compensates. Each parameter is explained with meaningful defaults and guidance, such as namespace defaulting to the vcluster name and server being needed for ingress or load balancer scenarios.

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 opens with a specific verb and resource: 'Export a vcluster kubeconfig to a file without switching contexts.' It immediately distinguishes this tool from vcluster_call, so an agent can tell them apart without opening the schema.

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?

It explicitly states when to use the tool: 'when you need credentials to hand to another tool,' and gives concrete examples like kubectl and Helm. It also names the alternative, vcluster_call, and explains the key difference: this tool leaves the current kube context untouched.

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