Restart container

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

No annotations exist, so description must cover behaviors. It lacks details on side effects (downtime, force-kill behavior), required permissions, or that restart stops then starts the container. The timeout parameter hints at force-kill but is not explained in text.

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 (two sentences) but omits critical details. It is front-loaded with purpose but lacks structure for readability. Every sentence earns its place, but content is sparse.

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 and no annotations, the description should explain return values and effects. It does not mention what happens post-restart, nor does it differentiate from sibling tools like start_container or compose_restart.

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 description coverage is 100%, providing adequate parameter meanings (container name/id, timeout). The description adds no extra value beyond the schema, achieving baseline score.

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 the verb 'restart' and resource 'container'. The phrase 'go-to fix for turn it off and on again style requests' adds context but does not explicitly distinguish from siblings like stop_container or compose_restart.

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?

Implies use for standard rebooting scenarios but provides no explicit guidance on when not to use it, or alternatives (e.g., stop->start, compose restart). Missing context for decision-making.

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