K8S Top

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

With no annotations, the description carries the full burden of behavioral disclosure. It implies a read-style metrics query via the kubectl command, but does not state whether it aggregates data, requires metrics-server, supports namespace selection, or how it behaves when metrics are unavailable.

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 compact sentence and is front-loaded, but it is more under-specified than meaningfully concise. It includes no additional structure or detail to help an agent use the tool correctly.

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?

The kubectl command anchor provides a basic starting point, but the tool lacks documented invocation parameters, scope, and behavioral context. With no annotations and minimal description, it is incomplete for reliable agent use.

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 single 'params' parameter has 0% schema description coverage and the description never mentions it. An agent cannot determine what keys or flags to pass, although the parameter is optional and flexible.

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 'Ресурсы подов (kubectl top pods)' clearly identifies the resource (pods) and the operation (resource utilization via kubectl top). It is distinguishable from sibling k8s tools at a high level, though it lacks an explicit verb and does not explicitly contrast with similar tools like k8s_pods or k8s_describe.

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?

There is no guidance about when to use this tool versus alternatives, no mention of prerequisites such as a metrics-server, and no exclusions or namespace considerations. The description only states what the tool does, not when to choose it.

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