List Docker Containers

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

Annotations already declare readOnlyHint true, so the description adds value by specifying that only running containers are listed by default, and that the dev instance uses sudo to invoke docker. This behavioral nuance goes beyond the annotations' safety profile.

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 two sentences: the first states the purpose and output fields, the second gives instance guidance. It is front-loaded with the core function and contains no unnecessary words, earning its place with every sentence.

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 (3 parameters, no output schema), the description covers the essential aspects: what the tool does, what fields are shown, and how to select the target instance. It could mention pagination or limits, but is adequate for a container listing tool.

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 coverage is 100% with descriptions for all parameters. The description adds extra context for the 'instance' parameter, noting that docker is invoked via sudo on dev, which is not in the schema. This provides meaningful behavioral detail that aids correct parameter usage.

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 lists running Docker containers on the VPS, specifying the verb 'List' and resource 'Docker containers'. It distinguishes from sibling tools like vps_docker_logs and vps_docker_stats by focusing on container listing.

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 provides guidance on which instance to target (prod vs dev), but does not explicitly state when to use this tool versus alternative VPS tools (e.g., vps_docker_logs, vps_docker_stats). The instance choice is clarified, but no general when-to-use or when-not-to-use advice is given.

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