list_pods

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

No annotations are provided, so the description carries the burden, and it does add useful disclosure about what the response contains (status, readiness, restart counts) which substitutes for a missing output schema. However, it says nothing about default namespace behavior when the param is omitted, pagination/limits, or whether the call is scoped to all namespaces.

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 that names the resource, the scope, and the returned fields with zero filler or redundancy.

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 two-parameter read-only list tool with a fully documented schema, the description covers purpose, scope, and return content. The only real gap is behavior when namespace is omitted or whether label_selector is echoed, but nothing critical is missing for correct invocation.

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%, with both parameters fully documented in the schema (namespace default "default", label_selector example). The description adds only that results are namespace-scoped and never mentions label filtering, so 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+resource (list pods) plus scope (namespace) and the fields surfaced (status, readiness, restart counts). This distinguishes it from get_pod_logs and describe_pod reasonably well, though it never explicitly contrasts itself with describe_pod, which also targets pods.

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 when-to-use guidance and no mention of alternatives, despite siblings like describe_pod (single-pod detail) and list_deployments. An agent must infer that this is the 'many pods, summary view' tool from the name alone.

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