kubectl_logs

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

Annotations already declare readOnlyHint=true, indicating safe read operation. The description 'Get logs' aligns with this but adds no behavioral context beyond what annotations and parameter descriptions (e.g., follow parameter warning of timeouts) provide. No contradictions, but minimal added value.

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 a single, clear sentence with no wasted words. It could benefit from slightly more detail without becoming verbose, but it is appropriately concise for a straightforward 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?

Despite high schema coverage and annotations, the description omits crucial details like output format (text streaming), default behavior (e.g., tail lines, end of logs), and handling of multiple pods/nodes. A tool with 12 parameters and no output schema requires richer context.

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 coverage is 100%, with all 12 parameters having clear descriptions. The description does not elaborate on any parameter, so it adds no meaning beyond the schema. Baseline of 3 is appropriate.

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 logs from Kubernetes resources like pods, deployments, or jobs' clearly states the tool's action (get logs) and scope (Kubernetes resources). While it uses vague phrasing 'like', it effectively distinguishes from sibling tools like kubectl_get (which gets resources, not logs). It could be more precise by listing all enumerated resource types.

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 versus alternatives (e.g., exec_in_pod for interactive debugging, kubectl_describe for detailed status). The description is purely functional and does not mention use cases, prerequisites, or exclusions.

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