stop_stack

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

With no annotations, the description explains the non-destructive nature ('without removing them, so it can be started again later'). It could add more detail on state preservation but is adequate for a stop 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?

Two sentences: first explains purpose, second defines the parameter. No redundant words; highly 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?

The description covers the tool's action and parameter adequately for a simple stop operation. An output schema exists (not shown) likely describing return value, so the description is sufficiently complete.

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 has 0% description coverage, so the description adds essential meaning: 'unique name for this stack, used to group/manage its containers.' This clarifies the parameter's role.

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 all containers in a compose stack without removal, using specific verb 'stop' and resource 'stack'. It implicitly distinguishes from sibling 'remove_stack' which removes the stack.

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 use when wanting to stop a stack for later restart, but lacks explicit guidance on when to use this vs alternatives (e.g., 'stop_container' for individual containers, 'remove_stack' for deletion).

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