Список тарифов Kubernetes

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

The description discloses what data is returned and suggests usage context, which is sufficient for a simple list operation. Although annotations set readOnlyHint=false, the description itself does not contradict this; it simply describes a read-like operation without mentioning side effects, which are not expected.

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 two sentences: one to state the return values and one to state usage context. It is front-loaded, contains no redundant information, and every phrase adds value.

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 no-parameter list tool, the description fully covers the return fields and usage scenario. No output schema is provided, but the description compensates by explicitly enumerating the returned attributes (ID, type, CPU, RAM, Disk, Network, price).

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 no parameters, and the schema coverage is trivially 100%. The description does not need to explain parameters, and the baseline of 4 for zero parameters is appropriate.

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 uses a specific verb 'Возвращает' (returns) and clearly identifies the resource as tariffs for master and worker Kubernetes nodes, listing the exact fields (ID, type, CPU, RAM, Disk, Network, price). This distinguishes it from sibling tools like list_server_presets or list_balancer_presets.

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 explicitly states when to use the tool: 'Use before creating a cluster or node group.' It provides clear context but does not mention exclusions or alternative tools, so it misses a full when-not-to-use guideline.

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