describe_pod

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

Annotations already declare readOnlyHint=true and openWorldHint=false, covering the safety profile. The description adds the detail that the result includes status, container state, and conditions, which gives useful foresight about what the agent will receive. It does not disclose any additional behavior such as error conditions or formatting conventions, but given the annotations, the bar is lower and the description is adequate.

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, front-loaded sentence that immediately identifies the action and resource scope. Every word contributes meaning; there is no filler, preamble, or redundant repetition of tool name or schema fields.

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 that the tool has a defined output schema, it is not necessary to describe the return values further. The annotations cover read-only behavior, and the required parameters are standard context selectors. The description provides enough about the operation for it to be invoked correctly. A minor gap is the lack of any mention of what happens if the pod doesn't exist, but that is not essential for selection.

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?

Input schema has 0% description coverage for its three required parameters. The description mentions 'Pod' but does not explain that 'name' refers to the pod name, nor clarify cluster or namespace format. While the parameter names are self-explanatory in a Kubernetes context, the description does not compensate for the missing schema descriptions, leaving some ambiguity for agents unfamiliar with the tool's conventions.

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 operation ('Return') and the specific resource ('a Pod'), and enumerates the content: 'detailed status, container state and conditions'. This distinguishes it from the sibling list-oriented tools (list_clusters, list_api_resources), which operate on collections rather than a single pod.

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 implies when to use the tool: when you need detailed status of a specific pod rather than a list of resources. However, it does not explicitly mention alternatives or give any 'when not to use' guidance. The context is clear enough for a knowledgeable agent but the guidance is not explicit.

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