list_kubernetes_pods

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

readOnlyHint=true already tells the agent this is a safe read. The description adds value by naming the per-pod fields returned, but says nothing about result limits, pagination, default ordering, or behavior when a filter matches nothing — relevant for a list operation over a potentially large cluster.

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: resource and returned fields first, filters second. No redundancy or filler.

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?

With no output schema, the description usefully discloses the returned fields, which is the main thing an agent needs. However, for a zero-required-parameter list tool over a potentially large resource, the absence of any note on result volume, pagination, or the agent_id scope leaves a meaningful gap.

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 every parameter including node, status, agent_id, workload and namespaces is already documented. The description restates four of the five filters but omits agent_id, and adds no meaning (e.g. whether status matches a phase name exactly) beyond the schema. Baseline 3 applies.

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 Kubernetes pods") and names the fields returned: status, restart count, node. Clear purpose, but it does not distinguish itself from sibling listers such as list_kubernetes_nodes or list_kubernetes_workloads beyond the resource noun.

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 phrase "optionally filtered by namespace, workload, node or status" implies when this tool applies, and all filters being optional signals it can be called bare to list everything. No explicit exclusions or alternatives (e.g. when to use list_kubernetes_workloads instead) are given.

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