docker

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

Since no annotations exist, the description should bear the burden of behavioral disclosure. It only lists action names without indicating that start/stop/restart are mutating operations or that logs/stats are read-only, nor does it mention potential side effects, permissions, or state changes. The description adds minimal value beyond what the schema's enum already provides.

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 concise sentence that efficiently lists core actions. However, it omits 'restart' and 'images' from the schema, which could mislead the agent into thinking those actions are unsupported. Despite this, it remains appropriately brief and front-loaded.

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 multi-action tool with 3 parameters and no output schema, the description is under-specified. It does not explain return values, error conditions, or when each action is appropriate. The schema covers parameter details, but the overall context for invoking this tool safely and effectively is incomplete, especially given the mutating actions present.

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 already documents all three parameters with 100% coverage, including descriptions for action, container, and log_lines. The description merely repeats a subset of the action enum values and does not add extra meaning about parameter relationships, such as container being required for certain actions, which the schema already states. This meets the baseline but does not exceed it.

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 it manages Docker containers and lists concrete actions (list, start, stop, logs, stats), making the purpose understandable. It is distinct from sibling tools like run_command or manage_service because of the Docker-specific resource, though the verb 'manage' is generic and does not fully enumerate all schema actions (e.g., restart, images).

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 is provided on when to use this tool versus alternatives such as manage_service or run_command. The description does not specify prerequisites (e.g., Docker daemon) or exclusion criteria, leaving the agent to infer usage from the tool name alone.

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