k8s_pods

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does well by specifying safety requirements for the delete action and mentioning log filtering capabilities. However, it misses critical details like authentication needs, rate limits, error handling, or what the tool returns (especially since there's no output schema). The description provides some behavioral context but leaves significant gaps for a multi-action tool.

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 efficiently structured with a brief introductory phrase followed by a bulleted list of actions, each with just enough detail. Every sentence earns its place by clarifying action purposes or constraints (e.g., the confirm/dryRun requirement for delete). It's front-loaded with the tool's scope and avoids 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?

Given the tool's complexity (14 parameters, 6 actions) and lack of both annotations and output schema, the description is moderately complete. It covers the action spectrum and key constraints but falls short on behavioral details like return formats, error cases, or prerequisites. For a multi-action Kubernetes tool with no structured safety or output information, it should provide more comprehensive guidance to fully compensate.

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%, so the schema already documents all 14 parameters thoroughly. The description adds minimal parameter semantics beyond the schema—it mentions 'optional label selector' for list and 'filtering (severity, grep, time-based)' for get_logs, but doesn't provide additional syntax, format, or interaction details. This meets the baseline 3 when the schema does the heavy lifting.

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 tool's purpose as 'Manage Kubernetes pods' and enumerates six specific actions (list, get, delete, get_logs, get_status, summarize_logs), providing a comprehensive verb+resource scope. It effectively distinguishes this pod-focused tool from sibling tools like k8s_deployments or k8s_services, which target different Kubernetes resources.

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 clear context for when to use specific actions (e.g., 'list: List pods in a namespace with optional label selector'), and includes important constraints like 'delete: Delete a pod (requires confirm=true or dryRun=true)'. However, it lacks explicit guidance on when to choose this tool over sibling tools (e.g., k8s_deployments for deployment-level operations) or broader usage scenarios beyond the action list.

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