Все кластеры k8s аккаунта (по проектам)

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

The description clearly describes a read-only list operation, but annotations set readOnlyHint=false, which contradicts the description. No additional behavioral context (e.g., pagination, return format) is provided beyond the 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 a single, concise sentence that is front-loaded with the key information. It contains no filler or redundant content.

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 parameterless list tool, the description adequately conveys its purpose. However, it does not explicitly describe the return format or differentiate from similar sibling tools, and there is no output schema to compensate.

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 tool has zero parameters, so the description does not need to explain parameter semantics. According to the rubric, a baseline score of 4 is appropriate for tools with no parameters.

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 'Список всех Kubernetes-кластеров аккаунта с привязкой к проекту' (List of all account Kubernetes clusters with project binding), specifying the verb (list), resource (Kubernetes clusters), and scope (account, with project binding). This distinguishes it from project-specific siblings like list_project_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 account-wide usage by saying 'всех' (all), but does not explicitly say when to use this tool instead of alternatives like list_project_clusters or list_k8s_clusters. There is no when-not guidance or mention of alternative tools.

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