get_cluster_kubeconfig

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

With no annotations provided, the description fully covers behavioral traits: credential expiration, no standing credential, security warning about live credential (bearer token, cluster-admin), and instruction to treat as secret and not echo back. No contradiction.

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 moderately long but well-structured: front-loaded with purpose, then usage guidance, then security note, then output format, then parameter source. Every sentence adds necessary value, though it could be slightly shortened.

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 security-sensitive tool with one parameter, no output schema, and no annotations, the description is remarkably complete: covers purpose, usage, security behavior, return type, and parameter source. The agent has all needed context.

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 schema coverage is 100% for the single parameter. The description adds the same context as the schema (service_id from list_services), providing no additional semantic value beyond the schema.

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 the verb 'Fetch' and resource 'SHORT-LIVED admin kubeconfig', and contrasts with sibling tools (list_cluster_kubeconfigs, download_cluster_kubeconfig) by emphasizing the short-lived nature, making it distinct.

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?

Explicitly states when to use (one-off, interactive kubectl access) and when not to (standing automation), and provides alternative sibling tools (list_cluster_kubeconfigs + download_cluster_kubeconfig).

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