get_supervisor_kubeconfig

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

Annotations declare read-only, non-destructive, idempotent, and open-world behavior. The description adds crucial security context: the returned kubeconfig contains a short-lived session token and must be treated as a credential, not logged or shared. This goes beyond annotations and addresses important usage constraints.

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 clear header, security note, args list, and returns statement. No unnecessary words; each sentence adds value. Slight reduction possible but overall well-structured.

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 simplicity (2 parameters, no nested objects) and no output schema, the description covers purpose, security, parameter roles, and return type. It is complete enough for an agent to understand usage without ambiguity.

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 explains both parameters: 'namespace' as the vSphere Namespace (context) and 'target' as the vCenter target name. This adds semantic meaning that the schema lacks, effectively compensating for low coverage.

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 'Get kubeconfig for the Supervisor K8s API endpoint,' specifying the verb and resource. It distinguishes from sibling tools like get_tkc_kubeconfig by targeting the Supervisor API, making purpose unambiguous and differentiated.

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 explicit guidance on when to use this tool versus alternatives such as get_tkc_kubeconfig. It lacks when-not conditions or suggestions for alternative tools, leaving the agent without context for correct selection.

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