stop_container

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

The description explains the effect (stop), the timeout parameter for forced termination, and the return value (container attrs). Annotations provide readOnlyHint and destructiveHint, but the description adds meaningful behavioral context.

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 very concise, front-loading the purpose in the first line and using a clear docstring format with args and returns. Every sentence is necessary and well-structured.

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?

For a simple stop tool, the description covers the purpose, parameters, and return value. It could mention that the container must be running, but that is generally implied. The lack of an output schema is compensated by the description of the return value.

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 description explains each parameter: id_or_name as 'The container id or name' and timeout as 'Seconds to wait before forcing termination'. This adds significant value beyond the schema which only provides types and defaults.

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 'Stop a container' which is a specific verb and resource. It distinguishes itself from sibling tools like kill_container by naming, but does not explicitly differentiate.

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 guidance on when to use this tool versus alternatives like kill_container or pause_container. The description lacks context on appropriate usage scenarios.

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