list_k8s_resources

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

The description is minimal; it only indicates a read operation. No information about data volume, pagination, or timeout. With no annotations, this is inadequate for an agent to understand the tool's behavior.

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?

Very concise (one sentence) but lacks sufficient detail for a generic tool with 7 parameters. Could be expanded slightly to improve clarity without becoming verbose.

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?

The description is too brief for a generic resource listing tool. It does not explain the relationship between parameters, the return format, or usage conventions. Output schema is missing, but description doesn't 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 descriptions already fully cover parameters. The tool description does not provide additional semantic detail beyond restating the core parameters.

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) and the primary identifiers (group/version/resource). It distinguishes from specialized list tools like list_pods by being generic. However, it omits mention of optional filtering parameters.

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?

No explicit guidance on when to use versus sibling tools like list_pods or list_statefulsets. The agent must infer from the generic nature.

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