compose_down

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

No annotations are provided, so the description must carry the full burden of explaining the tool's destructive behavior. While 'stop and remove' signals some destructive action, it does not disclose that this also removes associated networks, that volumes are only removed when the volumes parameter is set, or that orphan containers may be removed based on removeOrphans.

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 with no filler or redundant phrasing. The core action is front-loaded and immediately understandable.

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 that this is a destructive operation with no annotations and no output schema, the one-line description is not complete enough for an agent to safely reason about consequences. Information about what gets removed by default, when to avoid this tool, and how the projectName parameter scopes the operation is missing.

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 has 100% parameter description coverage, so the schema already explains all four parameters. The tool description provides no additional parameter-level context about how file, volumes, projectName, or removeOrphans affect the teardown behavior, so it does not elevate the baseline.

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 phrase, 'Stop and remove Docker Compose services,' which clearly identifies the operation and resource. It is easily distinguished from siblings like compose_up, compose_ps, compose_logs, and compose_build, and from stop_container/remove_container which target individual containers rather than a Compose-managed group.

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 tearing down a Docker Compose stack, but it does not explicitly state when to choose this tool over alternatives such as stop_container or remove_container. There are no exclusions or conditions given, so an agent must infer the intended use from the name and sibling context.

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