get_tkc_kubeconfig

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description adds significant behavioral context: the kubeconfig contains a short-lived session token, and guidance for writing to file vs inline return. No contradiction with annotations.

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 very concise: one line for purpose, three lines for security, and a bullet-style Args list. Information is front-loaded and well-organized, with no unnecessary words.

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 4 parameters (2 required), no output schema, and rich annotations, the description covers the essential behavior and main parameters. It lacks explanation of the 'target' parameter, and could mention the return format or token lifetime, but overall is sufficient.

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%, so the description must compensate. It documents 3 of 4 parameters (name, namespace, output_path) with clear semantics. The 'target' parameter is not mentioned, leaving a gap for an uncovered optional parameter.

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 starts with '[READ] Get kubeconfig for a TKC cluster,' which is a specific verb and resource. It clearly distinguishes from sibling tools like get_supervisor_kubeconfig (for supervisor cluster) and get_tkc_cluster (for cluster info).

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 includes a security note advising to prefer writing to file over returning inline to reduce credential exposure. It provides clear context for choosing output_path, but does not explicitly mention when not to use this tool or name alternatives.

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