kubectl_describe

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

Annotations already declare readOnlyHint=true, so the agent knows it's a read operation. The description adds minimal context beyond that, stating it 'describes' resources. It does not contradict annotations, but does not disclose additional behavioral traits like error handling or output format.

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 concise and front-loaded with the action ('Describe') and the resource ('Kubernetes resources'). Every word is relevant, and there is no redundancy.

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?

The description adequately conveys the basic purpose but lacks detail on what 'describe' returns (detailed info vs. summary), error handling, or how it differs from siblings like kubectl_get. Given no output schema and minimal annotations, a slightly richer description would enhance completeness.

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%, so baseline is 3. The description reinforces the purpose of resourceType, name, and namespace but adds no extra meaning beyond the schema's parameter descriptions. Context and allNamespaces are not elaborated, which is acceptable given schema covers them.

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 the tool describes Kubernetes resources, specifying the key parameters (resource type, name, optionally namespace). It is specific and distinct from siblings like kubectl_get (which lists resources) or kubectl_logs (which retrieves logs).

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 explicit guidance on when to use this tool versus alternatives (e.g., kubectl_get for listing, kubectl_logs for logs). There is no mention of when not to use it or what prerequisites are needed.

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