container_restart

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

Annotations already indicate non-readonly and non-destructive behavior. The description adds that stop_timeout_seconds controls graceful stop before SIGKILL, which is useful. However, it does not disclose side effects like interruption of running processes or network state changes.

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 extremely concise, using a clear structure with labeled arguments and return value. Every sentence is necessary and provides direct value.

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 basic operation and return value (dict of attrs), which is sufficient for a simple tool with two parameters. However, it lacks notes on prerequisites (e.g., container must exist) or error handling, but overall it is adequately 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?

With 0% schema description coverage, the description compensates by explaining both parameters: id_or_name as container identifier and stop_timeout_seconds as timeout for graceful stop. This adds meaningful context beyond the schema's type and default.

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 'Restart a container,' which is a specific verb-resource combination. While it distinguishes from siblings like container_stop and container_start, it does not explicitly differentiate that restart combines stop and start, leaving some ambiguity.

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 when to use the tool (when a container needs to be restarted) but provides no explicit guidance on alternatives or when not to use it. No exclusions or comparisons to siblings like container_kill are given.

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