docker_exec

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

With no annotations, the description must disclose behaviors. It covers timing and background job behavior but omits details like error handling, permissions, or exit code handling. Basic behavioral context is provided, but significant gaps remain.

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 (two sentences) and front-loaded with guidance. The redundant opening phrase 'Kali Agent MCP tool: docker_exec' adds no value, but overall it is efficiently structured.

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 10 parameters, no schema descriptions, and no output schema detail, the description is incomplete. It lacks fundamentals like return format, error modes, prerequisites, and environment variable usage, making it insufficient for reliable agent 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%, so the description must compensate. It only vaguely mentions timing parameters without definitions and ignores required parameters (container, command). This provides minimal added meaning beyond parameter names.

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 implies executing a command in a Docker container by referencing execution timing and Docker context, but it does not explicitly state the primary action. The focus on timing parameters makes the purpose clear enough, though it lacks differentiation from sibling tools like docker_run.

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 explicit guidance on choosing timing parameters and on_timeout values for different scenarios (background vs synchronous), which helps the agent decide usage. However, it does not compare with alternatives like exec_command or docker_run, missing when-not guidance.

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