Информация о Kubernetes-кластере

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

The annotations declare readOnlyHint: false and openWorldHint: true, while the description states it merely 'Возвращает' (returns) information, implying a read-only operation. This directly contradicts the annotations. The description provides no explanation for the non-read-only or open-world behavior, leaving the agent with conflicting signals.

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 a single, concise sentence that front-loads the action and lists the returned data fields without unnecessary words. It effectively communicates the tool's core functionality in a compact form.

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 low-complexity tool with only one parameter and no output schema, the description covers the purpose, parameter, and return fields. However, the contradictory annotations (readOnlyHint false, openWorldHint true) create a significant gap in behavioral context that the description fails to address, making the overall picture incomplete.

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 covers the single parameter cluster_id with a clear description ('ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID кластера'), and the description reinforces that the tool operates by cluster ID. However, the description adds no extra semantic detail about the parameter beyond what the schema already provides.

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's purpose: 'Возвращает детальную информацию о Kubernetes-кластере по его ID' (returns detailed info about a Kubernetes cluster by its ID) and enumerates the specific fields returned (имя, статус, версия, драйвер, ресурсы, зона, ingress). This distinguishes it from sibling tools like get_k8s_cluster_resources or get_k8s_kubeconfig.

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 when you have a cluster_id and need detailed cluster info, but it does not explicitly state when to use this tool versus alternatives like list_all_project_clusters or get_k8s_cluster_resources. No exclusions or alternative suggestions are provided.

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