get_k8s_resource

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

No annotations are present, so the description carries full burden. It only says 'Generic read', which weakly implies a safe read-only operation, but does not explicitly state the HTTP method, error behavior, or any side effects. Additional context like authentication or rate limits is missing.

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 a single sentence of 10 words, front-loading the purpose ('Generic read') and clearly stating the identification method. Every word is necessary; no fluff.

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 absence of an output schema, the description should mention what the response contains (the resource object). It also lacks guidance on using optional parameters like 'cluster' or 'namespaced'. The schema compensates for parameter details, but overall completeness is marginal.

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 parameters. The description adds minimal value by summarizing the key identifiers (group/version/resource/name) in a single phrase, but does not provide new information beyond what the schema offers.

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 it is a generic read tool that retrieves a single Kubernetes resource identified by group/version/resource/name. It distinguishes from sibling tools which are specific to resource types (e.g., describe_pod, list_pods) by using 'generic read', but doesn't explicitly contrast with describe_* tools that provide detailed output.

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 'Generic read' implies it should be used for basic retrieval, but no explicit when to use vs. alternatives is given. No exclusions or sibling tool mentions are provided, leaving the agent to infer context.

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