vcluster_list

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

With no annotations provided, the description carries full burden for behavioral disclosure. It explains internal client setup, serialized JSON return format, error behavior, and default kubeconfig handling. It does not mention side effects, but the read-only nature is implied by 'List'. No contradictions with annotations exist.

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 with a summary sentence, behavioral details, and clearly labeled Args and Returns sections. It is front-loaded and efficient, though there is minor redundancy between the first sentence and the second sentence.

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 simple list tool with one optional parameter, the description covers purpose, behavior, parameter semantics, and return format. It lacks details about error object structure or permission requirements, but these are not critical. Overall, it is sufficient for selecting and invoking the tool.

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 input schema only defines kubeconfig_path as an optional string/null with default null. The description adds full meaning: 'Optional path to a kubeconfig file. If not provided, the default kubeconfig from the environment will be used.' Given 0% schema description coverage, this compensation is complete.

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 'List all vclusters in the current Kubernetes context,' clearly stating the verb (List), resource (vclusters), and scope (current Kubernetes context). This distinguishes it from sibling tools like vcluster_describe, which targets a single vcluster.

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 notes the current Kubernetes context and the optional kubeconfig path, providing context for when the tool can be used. However, it does not explicitly mention when to prefer this over alternatives like vcluster_describe, nor does it state any exclusions. Usage is implied but not directly addressed.

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