manage_docker_containers

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

With no annotations provided, the description carries full responsibility. It explicitly declares read-only behavior and notes the hard cap on log tail lines to protect the LLM context window, disclosing important runtime constraints.

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 main description is a single, focused sentence that lists actions and explicitly excludes mutations. The schema descriptions are also concise, with no redundant or filler content.

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?

The description and schema together fully cover what the tool does, its inputs, defaults, and important safety details (read-only, log cap). No critical information is missing for an agent to correctly invoke it.

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?

Although the top-level schema description coverage is 0%, the nested input schema includes detailed descriptions for each parameter (action, container_id, include_stopped, log_tail_lines), explaining their purpose, defaults, and constraints (e.g., minimum/maximum for log_tail_lines).

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's verb (introspection), resource (Docker containers), and specific actions (list, inspect, fetch logs). It distinguishes itself from sibling tools (get_system_metrics, analyze_local_logs) by focusing on Docker-specific operations.

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 explicitly states what the tool does NOT do (does not start/stop/restart/remove containers), providing clear guidance for when not to use it. It also names the valid actions, giving a quick reference for operation selection.

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