kubectl_get

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

Annotations provide readOnlyHint: true, so no behavioral traits beyond read-only are needed. The description does not add any additional context like 'does not modify state' or authorization requirements. No attempt to disclose behaviors beyond the annotation.

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 that is clear and front-loaded. Every word contributes to conveying the core function. No wasted or redundant language.

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?

Despite 9 parameters and no output schema, the description only covers the basic intent. It omits capabilities like output formats, label/field selectors, all-namespaces, and sorting. The minimal overview does not fully inform the agent of the tool's capabilities, lacking completeness given the tool's complexity.

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 detailed parameter descriptions. The description adds minimal meaning beyond schema, only reiterating 'resource type, name, and optionally namespace'. Baseline 3 is appropriate as the description does not enhance parameter understanding.

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 'Get or list Kubernetes resources by resource type, name, and optionally namespace', indicating a specific verb and resource. However, it does not distinguish from siblings like kubectl_describe, which retrieves detailed information. The purpose is clear but lacks differentiation.

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 on when to use this tool versus alternatives. Siblings include kubectl_describe for detailed info and kubectl_logs for logs, but the description does not mention exclusions or provide context for choosing this tool over others.

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