get_pod_logs

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

With no annotations provided, the description carries the full disclosure burden. It clearly conveys a read-only fetch behavior and adds the important nuance that previous=True retrieves logs from the last crashed instance. It does not discuss permissions or edge cases, but the core behavioral trait is well disclosed.

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 purposeful sentences, front-loaded with the main action and then providing the most important parameter guidance. No filler or repetition.

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 that an output schema exists and the tool has a clear read-only purpose, the description is largely complete. It covers the primary use case, the optional container, and the crucial previous behavior. It could be more explicit about scope alternatives, but nothing essential is missing for basic correct invocation.

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 clarifies the container and previous parameters, and 'recent' loosely maps to tail_lines. However, it does not add detail about namespace or tail_lines semantics beyond what the schema titles already imply.

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 opens with a specific verb and resource: 'Fetch recent logs for a pod (optionally a specific container).' This clearly distinguishes the tool from siblings like list_pods, describe_resource, and exec_in_pod, and it immediately communicates the tool's core operation.

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 gives a concrete usage context: 'usually what you want after a CrashLoopBackOff.' It also explains when to set previous=True. It does not explicitly name alternatives or when not to use this tool, but the usage context is clear enough to guide an agent.

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