get_pod_status

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

The description discloses the return contents (phase, readiness, etc.) and implies it is a read-only operation by stating 'Returns the detailed status.' Without annotations, it carries the disclosure burden adequately.

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?

Two sentences, no redundant words. The first sentence lists outputs, the second provides usage guidance. Every sentence serves a purpose.

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 no output schema, the description adequately explains the returned data. The tool is simple (single pod status), and the description covers all needed context for the agent to decide to use it.

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% with both parameters (podName, namespace) described. The description adds no additional parameter semantics beyond what the schema provides, so baseline 3 is appropriate.

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 it returns detailed status of a single pod, listing specific fields like phase, readiness, restart count, etc. It distinguishes from sibling tools like get_pod_logs and get_recent_events by focusing on pod health status.

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?

Provides explicit guidance: 'Use this to dig into why a specific pod is unhealthy.' This implies when to use it, though it does not explicitly exclude cases like checking logs or events.

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