get_docker_info

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

No annotations are provided, so the description carries the transparency burden. It discloses that the tool is read-only via Docker API and is fatal if the daemon is unreachable, which are important behavioral traits. It does not mention limits or pagination, but for a simple inventory read, this is sufficient.

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 concise and front-loaded: it immediately states the main output, then adds safety and error behavior, and finishes with usage guidance. Every sentence provides value and there is no redundant information.

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 the tool's simplicity (no parameters) and presence of an output schema, the description is complete. It specifies the scope of returned data, read-only guarantee, failure mode, and appropriate usage, making it well-rounded for an agent to select and invoke correctly.

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 tool has zero parameters, so the baseline is 4. The description does not need to explain parameter semantics since there are none. The empty schema is fully covered, and the description adds context about what is returned rather than parameter details.

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 returns Docker containers (including stopped) and images, using specific verbs and resources. It distinguishes itself from siblings by highlighting 'including stopped' and aligning with 'Docker inventory' while pointing to get_docker_system_snapshot for a fuller view.

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 says 'Use for a Docker inventory; get_docker_system_snapshot for a fuller view,' providing direct when-to-use guidance and naming an alternative. It also notes the read-only nature and fatal failure condition, which helps selection decisions.

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