list_pods

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

No annotations are provided, so the description must carry the burden. It reveals sorting behavior (unhealthy pods first) but lacks details on authentication, side effects, pagination, or output format. The description is minimally transparent.

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 very concise (two sentences) and front-loads the purpose. However, it lacks structural elements like paragraphs or bullet points, and may be too terse for complete understanding.

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 (1 optional parameter) and the presence of an output schema (not shown in input), the description is adequate but incomplete. It does not mention pagination, default namespace behavior, or distinguish from similar listing tools like list_deployments.

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%, so the description must compensate. It adds that namespace is optional but does not explain its filtering effect or provide any additional semantics beyond the schema's sparse definition. The description adds limited value.

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 ('list pods') and the resource ('pods'), and distinguishes from siblings like delete_pod and pod_logs. The mention of optional namespace filtering and sorting by health adds specificity.

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?

It indicates that namespace is optional and that unhealthy pods sort first, but provides no explicit guidance on when to use this tool versus alternatives (e.g., cluster_summary, list_deployments) or when not to use it.

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