get_pod

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

No annotations are provided, so the description must disclose behavioral traits. It only states that it retrieves detailed information, offering no specifics about return format, error behavior (e.g., missing pod), or permissions. The read-only nature is implied but not elaborated.

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 with no fluff. It is concise and easy to parse, though it sacrifices substance for brevity. The length is appropriate for a simple get operation.

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 read tool with 3 parameters, no output schema, and no annotations, the description is too sparse. It does not explain what 'detailed information' includes, how parameters interplay, or how this tool differs from similar getters. This leaves the agent with insufficient context to use 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?

Schema coverage is 0%, so the description must compensate for parameter meaning. It does not explain the parameters at all. However, the parameter names (name, namespace, cluster_alias) are fairly self-explanatory, and the phrase 'specific Pod' clarifies the primary parameter, providing minimal additional context beyond the schema.

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 uses a specific verb ('Get') and resource ('Pod'), making its purpose clear. While it doesn't explicitly distinguish from sibling tools like get_pod_logs or get_pod_events, 'detailed information' likely refers to the full pod object/status, which is a reasonable reading.

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 no guidance on when to use this tool versus alternatives. Given the large number of pod-related sibling tools (get_pod_logs, get_pod_events, top_pod, etc.), explicit usage context or exclusions would be valuable, but none are provided.

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