List Docker Projects

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

No annotations exist, so the description must disclose behavior. It only states 'List' without explaining return format, whether it requires a running VPS, or any side effects. This leaves the agent guessing about the output structure.

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 front-loaded with the action verb. Every word contributes meaning; there is no redundant 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?

With no output schema, the description should specify what 'list projects' returns. It also lacks any note about relationship to vps_docker_containers or vps_docker_get. For a simple tool, it is barely adequate but incomplete.

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 single parameter vm_id is fully documented in the schema (Virtual machine ID), so schema coverage is 100%. The description adds no additional meaning beyond the schema, but the schema is sufficient for a single required parameter.

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 uses a specific verb ('List') and resource ('Docker projects') with scope ('on a VPS'), clearly indicating its read-only enumeration purpose. However, it does not explicitly distinguish from the sibling tool vps_docker_containers, which may overlap in meaning.

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 on when to use this tool versus alternatives such as vps_docker_containers or vps_docker_get. No prerequisites or context for the required vm_id are provided.

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