docker_ps

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

The description exclusively discusses execution timing parameters (expected_runtime_seconds, timeout_seconds, etc.) and on_timeout behavior, but does not describe the primary action (listing containers) or any read-only nature. Annotations are absent, so the description fails to disclose basic behavioral traits.

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 short but wastes space on boilerplate ('Kali Agent MCP tool') and overly detailed timing instructions. It could be more concise and focused on the core functionality.

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?

With 6 parameters, 0% schema description, no annotations, and an output schema present, the description is severely lacking. It does not explain the tool's purpose, parameters, or behavior, making it incomplete for effective use.

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%, and the description does not explain any parameter except on_timeout. Parameters like all_containers, timeout_seconds, etc., are not described, leaving the agent without essential semantic context.

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 only says 'Kali Agent MCP tool: docker_ps' without stating that it lists Docker containers. The name implies the purpose, but the description fails to clarify the specific action, making it vague.

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_ps versus alternative tools. Siblings include many Docker-related tools, but no comparisons or exclusions are provided.

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