control_docker_container

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

No annotations are provided, so the description carries the full burden of disclosure. It does not mention the destructive 'remove' action, nor does it describe side effects, permissions, or return values. This is a significant gap for a control tool that can delete containers.

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, front-loaded sentence that is appropriately concise. It loses a point because it fails to mention the 'remove' action, making it incomplete despite its brevity.

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?

For a tool with two simple parameters and no output schema, the description still leaves gaps: it omits an accepted action, provides no behavioral context, and offers no guidance on side effects or edge cases. The tool is more complex than the description suggests, especially given the destructive remove action.

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 input schema describes both parameters with 100% coverage, including the allowed action values. The description adds no additional meaning beyond what the schema already provides, so it meets the baseline but does not enhance parameter understanding.

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 starts, stops, or restarts Docker containers on the NAS, using specific verbs and a resource. However, it omits the 'remove' action that is present in the schema, making it incomplete. It is distinct from sibling tools, which are read-only or listing tools.

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 implied usage is to control Docker containers, which is clear from the description. However, there is no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. The context is present but not fully articulated.

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