Delete Docker Project

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

While the destructiveHint annotation already indicates this is a destructive operation, the description adds no extra behavioral context. It does not specify whether the deletion is permanent, whether associated containers or data are removed, or any other side effects beyond what the annotation already conveys.

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, compact sentence ('Delete a Docker project.') that is direct and easy to parse. Every word is meaningful, and it avoids any unnecessary elaboration or repetition.

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 simple schema and the destructiveHint annotation, the description is minimally sufficient to understand the basic action. However, it lacks details about potential side effects or prerequisites, such as whether the project must exist or whether all associated resources are removed. For a delete operation, this leaves some contextual gaps.

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 input schema already provides clear descriptions for both vm_id and project_name, achieving 100% schema_description_coverage. The description in the tool text adds no further semantic detail about the parameters, so it does not exceed the baseline of 3.

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 the specific verb 'delete' and identifies the resource 'Docker project', clearly differentiating it from sibling tools like vps_docker_create, vps_docker_get, and vps_docker_stop. It is unambiguous and aligns with the tool's name and title.

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 no guidance on when to use this tool versus alternatives such as vps_docker_stop or vps_docker_restart. It does not mention prerequisites, irreversible consequences, or any conditions that would warrant using this tool.

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