compose_stop

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

Discloses that containers, networks, and volumes survive (non-destructive). Annotations already indicate not read-only and not destructive; description adds specific survival context. Missing details about signal handling but is sufficient.

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?

Concise: two-line header then structured arg list. Every sentence adds value. No redundancy.

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 no output schema, description defines return value format (returncode, stdout, stderr, truncated). Covers all parameters and essential behavior for a stop operation.

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?

With 0% schema coverage, description fully describes all 6 parameters including defaults and how they map to CLI flags (e.g., stop_timeout_seconds becomes --timeout). Provides behavior for default 'all' services.

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 clearly states the tool stops services in a compose project without removing containers. It contrasts with compose_down and compose_start, distinguishing it from sibling tools.

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?

Explicitly explains when to use this tool: when you want to stop services but keep containers/networks/volumes intact. Mentions alternative compose_down and how to resume with compose_start.

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