container_stop

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

Describes the stopping process (stop signal then SIGKILL after timeout) and the server containerization restriction, adding context beyond minimal annotations.

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?

Very concise, no fluff. Front-loaded with purpose, then structured into args and returns sections.

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?

Covers purpose, usage, parameters, return value (exit code under State.ExitCode), and behavioral details. No gaps for this tool.

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?

Explains id_or_name as container id/name and stop_timeout_seconds as seconds between stop signal and SIGKILL. Schema coverage is 0%, so description fully compensates.

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?

Clearly states 'Gracefully stop a running container' and distinguishes from sibling tools like container_kill, container_restart, and container_pause.

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 recommends this over container_kill for clean shutdown, mentions container_restart and container_pause as alternatives, and notes restriction when server runs containerized.

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