k8s__describe_resource

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

No annotations are provided, so the description carries full burden. It only says 'Full describe for any resource type' but does not disclose output format, verbosity, potential errors, or required permissions. The agent lacks behavioral context beyond the basic operation.

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 under-specified; it is too short and lacks necessary details. While it is front-loaded, it is not concise enough to be useful—missing critical information makes it insufficient.

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 complexity of Kubernetes describe operations and the existence of many sibling tools, the description does not sufficiently differentiate this tool. No output schema exists, and the description fails to convey what information is returned or how it compares to tools like k8s__get_resource_usage.

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 0%, and the description adds no parameter-level information. The three parameters (name, namespace, resourceType) are not explained, e.g., valid resource types or namespace defaults.

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 'Full describe for any resource type' clearly indicates the tool performs a describe operation on any Kubernetes resource. It uses a specific verb (describe) and resource (any resource type), and it distinguishes from sibling list tools like k8s__list_pods which only list 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 no guidance on when to use this tool versus alternatives like k8s__get_resource_usage or k8s__diff_resource. It does not mention prerequisites, when not to use it, or how it differs from similar tools.

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