K8s Doctor MCP

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While it mentions the tool 'detects error patterns' and 'suggests causes and solutions', it doesn't describe what the output looks like, whether it's read-only or has side effects, performance characteristics, or any limitations. For a diagnostic tool with no annotation coverage, this leaves significant behavioral gaps.

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—a single sentence that efficiently communicates the core functionality with relevant examples. It's front-loaded with the main purpose and wastes no words. Every part of the sentence earns its place by adding value.

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's complexity (analyzing logs for errors with suggestions), lack of annotations, and no output schema, the description is insufficient. It doesn't cover what the output contains, how suggestions are formatted, error handling, or limitations. For a tool that presumably returns structured diagnostic information, this leaves the agent with inadequate context to use it effectively.

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 schema description coverage is 100%, so all parameters are documented in the schema. The description adds no additional parameter semantics beyond what's in the schema—it doesn't explain how parameters like 'namespace' or 'podName' relate to the log analysis process. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but also doesn't detract.

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 tool's purpose: 'Detects error patterns in logs and suggests causes and solutions' with specific examples like 'Connection Refused, OOM, DB errors'. This is a specific verb+resource combination that distinguishes it from siblings like 'check-events' or 'debug-crashloop', though it doesn't explicitly differentiate from 'diagnose-pod' which might have overlapping functionality.

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. It doesn't mention prerequisites, context for usage, or differentiate from sibling tools like 'diagnose-pod' or 'full-diagnosis' that might serve similar diagnostic purposes. The agent must infer usage from the tool name and parameters alone.

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