describe_pod

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

No annotations are provided, so the description must disclose behavior. It describes the content of the output (status, IP, node, etc.) but does not explicitly state that the operation is non-mutating, mention permission requirements, or describe error behavior. The read-only nature is implied by the verb 'describe' but not made explicit.

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 concise and well-structured: a one-sentence summary followed by a clearly labeled Args list. Every sentence provides useful information, and the format is easy to scan.

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 simple describe tool with a supported output schema, the description covers the main elements: purpose, parameters, and the nature of the returned data. It does not address error scenarios or emphasize pod_name as required, but given the simplicity and available output schema, it is largely complete.

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 has 0% description coverage, so the description's Args section adds crucial meaning: it explains that cluster accepts 'local' or 'cloud' (with context), and provides defaults for namespace and cluster. However, it does not highlight that pod_name is logically required despite the schema listing an empty default, which is a minor gap.

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's function: retrieving detailed information about a specific pod, listing fields like status, IP, node, container status, restart count, image, and resource configuration. This is a specific verb-resource combination that distinguishes it from sibling tools like list_pods and get_pod_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?

The description implies usage for inspecting a single pod but does not explicitly state when to use this tool versus alternatives such as diagnose_pod or get_pod_logs. There are no explicit exclusions or alternative recommendations, leaving the agent to infer the appropriate context.

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