get_tkc_kubeconfig

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

Annotations already indicate safe read operation (readOnlyHint=true, destructiveHint=false). Description adds crucial context: returned kubeconfig contains a short-lived session token, and explains security trade-off between inline vs file output. No contradictions.

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?

Well-structured with sections and bullet-like args. Front-loaded with purpose and security note. Slightly verbose but efficient overall.

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?

Covers main behavior (return string or write file) and security, but misses explaining the 'target' parameter. No output schema, so return behavior description is helpful. Lacks full coverage of all inputs.

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?

Input schema has 4 parameters (name, namespace, output_path, target) with 0% schema description coverage. Description explains 3 of them but completely omits the 'target' parameter, leaving its purpose undocumented.

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 starts with '[READ] Get kubeconfig for a TKC cluster,' specifying the verb and resource. It distinguishes from sibling 'get_supervisor_kubeconfig' by focusing on TKC clusters.

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?

Provides explicit guidance to prefer writing to file over inline return to reduce credential exposure. Lacks when-not-to-use or comparison to siblings, but sufficient for common usage.

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