list_failing_pods

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

With no annotations, the description carries the burden. It explains the filtering behavior (pods in error states) and gives a sample list. However, it omits any mention of permissions, cluster/namespace behavior, or side effects. For a read-only list tool this is somewhat acceptable, but the lack of scope disclosure (e.g., how cluster_alias is used) limits transparency.

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, well-structured sentence that front-loads the core purpose and uses concrete examples to convey the exact criteria. 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?

While the tool is relatively simple and an output schema exists, the description lacks any parameter semantics and does not explicitly guide the agent on namespace/cluster scoping or when not to use it. Adequate but incomplete for a tool without annotations.

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 does not mention the parameters (namespace, cluster_alias) at all. The agent gets no help understanding how these parameters affect the query. This is a significant gap.

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 uses a specific verb ('List') with a resource ('pods') and further scopes it to 'error states' with concrete examples (CrashLoopBackOff, ImagePullBackOff, etc.). This clearly distinguishes it from sibling tools like list_pods and list_pods_not_ready.

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 implies when to use the tool (when you want to see failing pods) by listing error states, but it does not explicitly compare with alternatives like list_pods_not_ready or provide explicit exclusion criteria. Usage context is present but understated.

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