Get pod

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

With no annotations, the description carries the full burden of behavioral disclosure. 'Fetch' implies a read operation, but the description does not say what the returned representation includes, whether it requires special permissions, or what happens on errors. This leaves important behavior unspoken.

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?

A single 13-word sentence that starts with the action and the specific result. Every word contributes to meaning, there is no redundancy, and the structure is front-loaded.

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 description is enough for a trivial getter in that the schema already covers required and optional parameters, but with no output schema and minimal wording, it does not explain the return shape or edge case. The description is adequate but not self-contained for a complex agent needing to handle failures or requiring specifics of 'full representation'.

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 input schema already documents all three parameters at 100% coverage (name, namespace, context with default). The description adds no additional meaning beyond the schema, so it simply meets the baseline without strengthening param understanding.

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 ('Fetch') and resource ('full representation of a single pod'), clearly distinguishing it from siblings like list_pods (collection) and get_pod_logs (logs only). The phrase 'single pod' makes the target unambiguous.

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 word 'single' implies this tool is for fetching one pod's details rather than listing all pods, but the description does not explicitly state when to choose this over list_pods or get_resource. No alternatives are named and no exclusions are communicated.

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