restart_container

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

Beyond the idempotentHint annotation, the description adds no behavioral context. It doesn't disclose that restart typically stops then starts a container, or what happens if the container doesn't exist. The annotation covers idempotency, but other behavioral traits are omitted.

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, clear sentence with no unnecessary words. It is appropriately minimal for a straightforward operation, and the structure is perfectly concise.

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 the tool's simplicity (1 parameter, no output schema) and the annotation, the description is minimally sufficient for a basic operation but lacks critical contextual info. It doesn't explain implications (e.g., stopping/starting), potential errors, or when to prefer this over stop/start. The presence of many sibling tools and no additional explanation makes it incomplete for an AI agent to choose correctly.

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 0%, and the description does not compensate. The only parameter 'container' is a string with no explanation in either the schema or the description. The phrase 'Restart a container' implies the 'container' argument but gives no details about format, valid values, or meaning.

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 action (restart) and the resource (container). It distinguishes from sibling tools like start_container and stop_container because 'restart' implies a distinct operation. However, it lacks explicit detail such as 'stop and start' which could add clarity.

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 provides no guidance on when to use this tool versus alternatives like start_container or stop_container. There are no usage scenarios, exclusions, or mentions of related tools despite many siblings being available.

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