docker_ps

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

Discloses read-only nature, technical method (SSH docker inspect with sudo -n fallback), and lists two specific error types. With no annotations, the description carries full burden and reasonably covers behavioral traits for a list tool.

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?

Two tightly packed sentences: first states function and output fields, second adds technical details and errors. No superfluous words.

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?

Describes return JSON structure with field names, error types, and read-only semantics. Lacks output schema, but the description compensates adequately. For a list tool with one parameter, coverage is high.

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 has 100% coverage with description 'Instance ID or name.' The tool description adds 'on one instance' but no new meaning beyond schema. Baseline 3 appropriate.

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?

Description clearly states 'List Docker containers' with specific fields returned (state, health, restart count, published ports, compose labels). Distinguishes from siblings like docker_events_summary (events), docker_logs (logs), docker_stats (stats) by listing its unique output fields.

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 explicit guidance on when to use this tool versus alternatives like docker_stats or docker_log_summary. Description implies single-instance use but doesn't provide criteria for selection among sibling tools.

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