pod_top

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

Discloses failure behavior when metrics-server is not installed (returns 'available: False' with a clear message). No annotations, so description carries burden adequately.

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?

Concise: one-line purpose, one-line behavior note, then parameter definitions. No wasted words.

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?

Covers purpose, prerequisite, failure case, and parameter usage. No major gaps; output shape is implied for a read tool.

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?

Provides clear usage for both parameters: namespace can be omitted for all namespaces, target is a k8s target from config. Schema coverage is 0%, so description adds necessary context.

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?

Starts with '[READ]' indicating operation type, clearly states it provides CPU/memory usage per pod, and implicitly distinguishes from 'node_top' sibling.

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?

Explicitly states prerequisite (metrics-server) and explains namespace usage ('omit for all namespaces'). No explicit when-not-to-use, but context is clear.

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