k8s_get_logs

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

No annotations are provided, and the description does not disclose behavioral traits such as whether it returns all logs or supports streaming, any rate limits, or permission requirements. The agent has no information beyond the basic function.

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 extremely concise at just three words. While it efficiently conveys the core purpose, it could be slightly expanded to include key details without becoming wordy.

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 the tool has four parameters, no output schema, and no annotations, the description omits important context such as return format (plain text, timestamps), behavior for non-existent pods, or whether it follows log rotation. For a logging tool, this is a significant gap.

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 provides 100% description coverage for all four parameters (pod, namespace, container, tail), so the schema already conveys parameter meaning. The description adds no additional context, meeting the baseline expectation for high coverage.

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 'Get pod logs' clearly states the verb (Get) and resource (pod logs), indicating the primary action. However, it does not explicitly differentiate from sibling tools like docker_logs, which also retrieves logs but for Docker containers rather than Kubernetes pods.

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 like k8s_exec_pod for debugging or k8s_list_pods for enumeration. There is no explanation of prerequisites or context (e.g., requires a running pod).

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