k8s_get_resource

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

With no annotations, the description must fully disclose behavior. It implies a read operation ('Get') but does not explicitly state read-only, required permissions, rate limits, or any side effects. Missing output schema leaves return format vague.

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 concise with two sentences and front-loaded purpose. However, conciseness sacrifices useful details; it could include parameter guidance or usage tips 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?

Given no annotations, no output schema, and many sibling tools, the description is incomplete. It lacks information on return format, error handling, and how to differentiate from similar tools. A more complete description would cover these gaps.

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 has 0% description coverage and the description adds no explanations for any of the 6 parameters (kind, name, group, etc.). Users get no help on how to specify parameters like group or version, which are optional and could be confusing.

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 gets the 'complete definition of a single Kubernetes resource' and returns 'spec, status, and metadata', which is specific and informative. However, it does not differentiate from similar siblings like k8s_get_resources (plural) or k8s_describe, missing a chance to clarify its unique purpose.

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 guidance is provided on when to use this tool vs alternatives (e.g., k8s_get_resources for listing multiple, k8s_describe for a detailed overview). The description lacks context about prerequisites, limitations, or preferred scenarios.

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