vcluster_call

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explains that the tool connects to a running vcluster, uses the server-side flag, and returns a CommandResult with exit code and output, or an error object. It also covers default namespace and kubeconfig behavior, providing useful operational context, though it could mention permission requirements or side effects more explicitly.

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 appropriately sized: a one-sentence summary, a brief mechanism explanation, then Args and Returns sections. Every sentence contributes value, and it is front-loaded with the primary purpose. No redundancy or unnecessary fluff.

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 arbitrary commands inside a vcluster) and the presence of an output schema, the description covers all essential aspects: connection method, parameters, defaults, and return behavior (success vs. failure). It is complete enough for an agent to invoke the tool correctly without additional information.

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 description fully compensates by explaining each parameter in detail: name, command (including quoting example), optional namespace with default vcluster-<name>, and optional kubeconfig_path with environment fallback. This adds substantial meaning beyond the bare schema property names and types.

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 explicitly states 'Execute a command inside a vcluster' with a specific verb and resource. It clearly distinguishes this tool from sibling tools like vcluster_describe or vcluster_pause by focusing on command execution within the virtual cluster, and further details the mechanism using 'vcluster connect'.

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 clear context on when to use this tool: to run commands inside a vcluster. It does not explicitly list alternatives or exclusions, but the purpose is distinct enough from siblings. The Args and Returns sections also set expectations for usage, making it easy for an agent to decide when to invoke it.

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