Create Docker Project

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

No annotations are provided, so the description carries full responsibility for disclosing behavior. It only states that a new project is created, but does not disclose whether it overwrites existing projects, what happens if the project name already exists, whether it validates the compose content, or what response to expect. This is a significant gap for a create operation.

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 with no filler or redundancy. It is front-loaded and communicates the core purpose immediately, earning a 5.

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 straightforward nature and well-documented parameters, the description is minimally sufficient. However, the absence of behavioral details (e.g., return value, failure modes) and no output schema means it is not fully complete for an agent to predict outcomes. It does neither exceed nor fall far short of expectations for a simple create 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 description coverage is 100%, with each parameter (vm_id, project_name, compose_content) having a clear description. The tool description adds no extra parameter meaning beyond what the schema already provides, so the baseline of 3 applies.

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 'Create a new Docker Compose project' uses a specific verb ('create') and resource ('Docker Compose project'), clearly distinguishing it from sibling operations like vps_docker_update, vps_docker_delete, or vps_docker_start. It precisely states what the tool does.

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 implies usage for creating a new project, but does not explicitly state when to use it versus alternatives like vps_docker_update, nor does it mention prerequisites (e.g., VM must exist) or exclusions. The purpose is clear enough that an agent can infer when to use it, but no explicit guidance is provided.

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