list_api_server_metric_names

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

No annotations are provided, so the description must fully disclose behavior. It only states that the tool lists metric names, implying a read-only operation, but does not mention any potential side effects, required permissions, or rate limits. The description lacks detail on what happens on errors or timeouts.

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 very short (one sentence), but it omits important details. While it avoids verbosity, the brevity sacrifices clarity and completeness, making it less useful than a slightly longer, more informative description.

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?

Given the tool has 4 parameters with 0% schema coverage and no annotations, the description is insufficient. It does not mention the output format (though an output schema exists), nor does it provide enough context for an agent to correctly invoke the tool or understand its behavior.

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?

Schema description coverage is 0%, and the description provides no explanation of the parameters (kube_context, kubeconfig_path, timeout_seconds, metric_name_pattern). The description does not clarify how these parameters affect the results, leaving the agent to guess their purpose and valid values.

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?

Description clearly states the tool lists metric names from the Kubernetes API server /metrics endpoint. However, it does not differentiate from the sibling tool 'get_eks_metrics', which might retrieve actual metric values or focus on EKS-specific metrics.

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?

No guidance on when to use this tool versus alternatives like 'get_eks_metrics'. There is no mention of prerequisites, recommended contexts, or situations where the tool should not be used.

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