docker_logs

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

With no annotations, description should disclose core behavior and side effects. It focuses on timing parameters but omits the primary action of reading logs. No mention of whether logs are fetched from stdout/stderr, or about container state requirements.

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?

Description is brief but redundant with 'Kali Agent MCP tool: docker_logs' header. The core timing advice is useful but could be condensed. No structural issues beyond upfront positioning.

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 9 parameters, 1 required, no description of required container parameter. Output schema exists but not referenced. Lacks essential context about log scope, streaming, or return format. Incomplete for effective 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%, yet description only explains timing-related parameters (5 of 9). No explanation of the required 'container' parameter or optional 'tail', 'since', 'timestamps'. Offers limited value over schema.

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?

Description does not explicitly state that this tool retrieves Docker container logs; purpose is only implied by tool name. No verb-resource statement or differentiation from sibling Docker tools like docker_inspect or docker_ps.

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 docker_logs versus other Docker inspection tools. Only provides timing execution advice, not usage context or alternatives.

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