Kubeconfig кластера

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

The warning that the content contains secrets and should not be published adds valuable sensitivity context beyond the annotations. However, it does not disclose other behaviors like required permissions or potential errors, which would improve transparency further.

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 exactly two sentences, front-loaded with the action ('Возвращает содержимое') and resource, with no wasted words. The security note is placed appropriately.

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 getter with one parameter and no output schema, the description covers the core purpose, the return value, and adds a security warning. It is sufficiently complete for an agent to select and invoke the tool correctly.

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 fully covers the only parameter cluster_id with a clear description ('ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID кластера'), and the tool description does not need to add more. Baseline 3 is appropriate given 100% schema 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 the tool returns the contents of the kubeconfig file for connecting kubectl to a cluster. This specific verb+resource combination distinguishes it from sibling tools like get_k8s_cluster or list_k8s_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?

The description implies usage for kubectl connection setup but does not mention when not to use it or provide alternatives. It gives context but no explicit exclusions or comparisons.

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