k8s_top_pods

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool shows resource usage but doesn't describe output format (e.g., table, JSON), whether it's real-time or historical, any rate limits, permissions required, or if it's a read-only operation. This leaves significant gaps for an agent to understand how to interpret results.

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, efficient sentence that directly states the tool's function without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 complexity of Kubernetes resource monitoring, no annotations, and no output schema, the description is incomplete. It doesn't explain what the output looks like (e.g., metrics format, units), whether it requires cluster metrics to be enabled, or how it differs from similar tools. This leaves the agent with insufficient context for effective 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?

Schema description coverage is 100%, so the schema already documents both parameters (namespace and all_namespaces). The description doesn't add any parameter-specific details beyond what's in the schema, such as how these parameters interact or default behaviors. This meets the baseline for high schema 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 states the tool's purpose with a specific verb ('Show') and resource ('resource usage for pods'), specifying CPU and memory metrics. It distinguishes from siblings like k8s_get_pod (which retrieves pod details) and k8s_top_nodes (which shows node metrics), though it doesn't explicitly mention these distinctions in the description itself.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention when to prefer k8s_top_pods over k8s_get_pod for resource metrics, or how it differs from k8s_top_nodes. There's no context about prerequisites, such as needing metrics-server installed in the cluster.

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