pod_list_tool

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

There are no annotations, and the description discloses no behavioral traits beyond the literal action. It does not mention read-only status, filtering behavior, pagination, or any side effects, leaving the agent with no safety or behavior cues.

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 extremely short but merely restates the tool name. It is under-specified rather than appropriately concise, failing to add any useful information beyond the name itself.

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?

Despite the simple parameter set and presence of an output schema, the description does not state that it lists all pods, mentions filtering, or describes the return format. Without annotations, this minimal description leaves key behavioral aspects unexplored.

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% and the single 'filters' parameter is well-described in the schema. The description adds no parameter information, but the baseline score of 3 applies because the schema fully documents the parameter.

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 'List pods' clearly states the verb (list) and resource (pods), unambiguously distinguishing it from sibling tools like pod_inspect, pod_start, and container_list. It fully identifies the operation.

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, such as pod_inspect or container_list. No context is given about typical use cases or exclusions.

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