k8s_pod_logs

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

The description adds '[SAFE]' hinting at non-destructive nature, but lacks details beyond that—e.g., whether it returns live or archived logs, format, or any side effects. No annotations provided to supplement.

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 is very concise but at the cost of missing critical information. The tag [SAFE] is helpful but not enough.

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?

For a simple logs tool, the description is incomplete. No mention of output format, maximum tail value, or pod-specific details. Without annotations or output schema, more context is needed.

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 has 3 parameters with no descriptions; the description adds no information about the parameters, their meaning, or valid values (e.g., tail format, namespace default).

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 action 'Retrieve logs' and the resource 'Kubernetes pod'. It distinguishes from sibling tools like k8s_pod_list and k8s_events.

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 guidance on when to use this tool vs alternatives (e.g., k8s_events for events). Does not specify context like pod status requirements or log source.

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