restart_container

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Restart a container' reveals nothing about side effects (e.g., downtime), required permissions, reversibility, or what the response will contain. This is a mutation tool with zero transparency beyond the action itself.

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 a single short sentence, front-loaded with the verb and resource. It contains no redundant words or filler, achieving maximum conciseness.

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?

With no output schema and no annotations, the description is expected to explain more. It fails to mention what happens after restart, whether the operation is synchronous, or any confirmation details. The schema covers parameters but not the broader operational context, leaving the description incomplete for an agent invoking the 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?

The input schema fully describes both parameters (containerId: 'Container ID or name'; environmentId: 'Portainer environment ID') with 100% coverage. The description adds no additional parameter guidance, so the baseline 3 is appropriate per the rubric.

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 'Restart a container' clearly states the specific action (restart) on a specific resource (container). This distinguishes it from sibling tools like start_container, stop_container, and recreate_container. However, it does not explicitly mention the Portainer context or contrast with these alternatives.

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 is provided about when to use this tool versus alternatives, preconditions (e.g., container must exist), or expected effects. The description is a bare action statement without any context for tool selection.

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