k8s_top_pods

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

With no annotations, the description must disclose behavioral traits. It reveals a dependency (metrics-server) and the breakdown by container. However, it does not mention read-only status, error behavior if metrics-server is missing, or output format. Adequate but not comprehensive.

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?

Two sentences, 14 words, no redundant information. Every sentence provides essential information (purpose, prerequisite, usage hint). Highly concise and well-structured.

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 simple tool with two parameters and no output schema, the description covers the main functionality, a prerequisite, and a key usage note. It could mention that the output includes CPU/memory per container, but the return format is not specified. Overall sufficient for the complexity.

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 coverage is 0% (no parameter descriptions). The description adds meaning for the 'namespace' parameter ('Omit namespace for all namespaces') but does not explain the 'context' parameter (required, likely kubeconfig context). Partial compensation for low coverage.

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 uses the verb 'display' with the resource 'CPU and memory usage of pods' and specifies 'broken down by container'. It distinguishes from sibling tools like k8s_top_nodes, so the purpose is specific and unambiguous.

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 states a prerequisite ('Requires metrics-server') and a usage hint ('Omit namespace for all namespaces'). It does not explicitly address when to use or alternatives, but the sibling list shows k8s_top_nodes for nodes, so usage context is clear.

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