Docker Compose Delete

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

With no annotations, the description carries the full behavioral burden. It does disclose two traits beyond the schema: it is a write operation (写操作) and it zeroes the project list (项目列表清零). However, it omits whether running containers are destroyed, whether the action is reversible, and what permissions are needed — significant gaps for a destructive 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?

A single compact sentence with no wasted words, and the core purpose is front-loaded. It is arguably under-specified rather than over-long, but structurally it is efficient.

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?

An output schema exists, so return values need not be explained. But for a destructive, unannotated delete with a required project_name and no stated side effects, reversibility, or auth requirements, the description is too thin to let an agent invoke it confidently.

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%, so all five parameters (host, port, scheme, profile, project_name) are already documented in the schema. The description adds nothing about parameter usage, 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?

States a specific verb+resource: '删除 Compose 项目登记' (delete the Compose project registration), which clearly identifies a removal operation and distinguishes it from the many compose siblings like docker_compose_create/start/stop. It stops short of naming which sibling to prefer, but the purpose itself is unambiguous.

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 when-to-use or when-not-to-use guidance. The phrase '项目登记' (registration) hints that this removes the project entry rather than stopping it, implying a distinction from docker_compose_stop, but the agent must infer that. No prerequisites or alternatives are stated.

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