k8s_describe

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

No annotations are provided, so the description should carry the burden of behavioral disclosure. It explains that the tool shows detailed information but does not mention side effects, error handling, or read-only nature. Minimal but not misleading.

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?

Two sentences with no wasted words. The first sentence states the core purpose, and the second adds key capability. Efficient and well-structured.

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 output schema and rich sibling context, the description is mostly complete. It explains how to specify resources and use all_namespaces. It could mention the output format or that it returns detailed YAML, but the kubectl analogy likely suffices for experienced users.

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?

With 0% schema description coverage, the description adds value by explaining that 'name' and 'selector' are for specifying resources, and 'all_namespaces' for cross-namespace search. It does not explicitly describe 'context', 'namespace', or 'resource_type', but 'resource_type' is implicit in the tool's purpose.

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 shows detailed information about a resource, explicitly compares to 'kubectl describe', and explains it can describe by name or label selector, which distinguishes it from sibling tools like k8s_get_resource.

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 context by referencing kubectl describe and explains the all_namespaces option. However, it does not explicitly state when to use this tool versus alternatives like k8s_get_resource or k8s_get_resources, which would improve guidance.

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