K8S Describe

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

With no annotations, the description carries the full burden. 'Describe' implies a read-only inspection and the parenthetical at least names what the output surfaces (conditions, events). However, it does not disclose required context such as cluster access, how the pod is selected, or any side-effect/error behavior, leaving notable ambiguity.

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 compact and front-loaded with no wasted words, which is good. But it is so sparse that it under-specifies the tool; the brevity comes at the cost of missing essential invocation details.

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?

For a Kubernetes introspection tool requiring a pod identifier and possibly a namespace, this description is not sufficient. The output schema may cover return shape, but nothing explains how to construct the input, making the definition incomplete for an agent trying to call it correctly.

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?

The schema lists only a generic free-form 'params' object with no properties and 0% schema description coverage, so the agent has no idea what keys are needed (e.g., pod name, namespace). The description does not compensate by naming any parameters, making correct invocation essentially guesswork.

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 identifies a specific verb ('Describe') and a specific resource ('pod') and adds the detail that conditions and events are included. This is clear enough to distinguish the tool from sibling list-style tools like k8s_pods and k8s_events, though it does not explicitly name any alternative.

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 given about when to use this tool rather than k8s_pods, k8s_events, or k8s_logs. The intended context can be inferred from the name and the word 'describe', but the description itself provides no explicit use cases or exclusions.

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