list_pods

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

Despite no annotations, the description correctly implies a read operation ('Lists'). However, it does not disclose error behavior (e.g., missing namespace), pagination, or output format. For a simple list, this is minimally acceptable but lacks depth.

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?

Single sentence, no redundant words, immediately conveys the purpose. Ideal conciseness.

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's simplicity (2 parameters, no output schema), the description is adequate but incomplete. It fails to mention what the returned list contains or any limitations, leaving the agent without enough context to interpret results.

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 100%, so the description adds no value beyond the parameter definitions. Baseline 3 applies; no extra context is provided for the parameters.

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 action ('Lists') and resource ('pods') with a scope ('in a specific namespace'), which is specific and unambiguous. However, it does not differentiate from sibling listing tools like list_nodes or list_jobs, missing the opportunity to distinguish its purpose.

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 is given on when to use this tool versus alternatives. With numerous sibling tools for listing other resources or getting pod details, the description should indicate typical use cases or comparison to describe_pod or get_pod_logs.

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