list_pods

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

No annotations are provided, so the description carries the full disclosure burden and does not meet it. It says nothing about whether results are paginated, what fields are returned, whether it lists all pods or only running ones, or what happens if the namespace has none.

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?

A single front-loaded sentence with no filler. It is efficient, though the brevity comes at the cost of the guidance and behavior details noted elsewhere.

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?

For a one-parameter read-only list tool with no output schema, the definition is minimally sufficient to call correctly. It falls short on return shape (no output schema means the description should say what a pod entry looks like) and on the default namespace value.

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 0%, but there is only one parameter and its name plus the phrase "in a namespace" make its meaning unambiguous. The description does not mention the schema's "default" default value, which is the one piece of non-obvious behavior an agent might need.

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?

States a specific verb and resource ("List pods") plus the scope ("in a namespace"). The resource name alone separates it from siblings like list_deployments, list_services, list_nodes, though the description never explicitly routes to or away from them.

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?

There is no statement of when to use this versus describe_pod, get_logs, or cleanup. The usage is only implied by the verb 'List' — an agent gets no guidance on selecting this tool for broad discovery versus inspecting a single pod.

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