describe_pod

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

The description describes read-only behavior ('Show detailed status...'), which aligns with the typical use. However, it lacks details on permissions, error handling, or side effects. Given no annotations, the description carries full burden but offers limited transparency beyond the obvious.

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?

Single sentence, front-loaded with verb and target, no wasted words. Efficiently communicates the tool's core function.

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?

The tool is simple and an output schema exists, reducing the need for return value details. However, missing context like availability of pod details or error scenarios keeps it from being fully comprehensive. Still adequate for a straightforward describe operation.

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 description coverage is 0%, so the description must compensate. It implies the pod name is needed ('single pod') but does not explain the namespace parameter, default value, or provide examples. This leaves the agent with minimal guidance beyond the schema field names and types.

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 verb 'Show' with specific details: 'detailed status, events, and configuration' for a single pod. It distinguishes from sibling tools like list_pods or get_pod_logs by focusing on a single pod's comprehensive details.

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 explicit guidelines on when to use or alternatives are provided. The description implies it is for inspecting a single pod, but does not mention when to prefer list_pods for all pods or get_pod_logs for logs require this tool.

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