docker_compose_restart

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

The description states that restarting changes server state, which is a key behavioral cue. However, no annotations are provided, so this is the only disclosure. It does not mention whether the tool is destructive, if it requires specific permissions, or what happens to running containers.

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 at two sentences with no extraneous information. It is front-loaded with the core action and follows with a single behavioral note.

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 that the tool has no annotations, no enum values, and 0% schema coverage, the description is insufficient. An output schema exists but the description doesn't hint at what is returned. More context about prerequisites, side effects, and default behavior is needed.

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 coverage is 0% (no parameter descriptions), and the description only implies that 'service' is an optional string. It doesn't explain what 'service' means (e.g., service name in compose file, format expectations, or default behavior when empty).

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 the action ('Restart Docker Compose services') and notes the side effect ('This changes server state'), which distinguishes it from inspection tools like docker_ps or docker_logs. However, it could be more specific about which Docker Compose services are affected (all or a given service).

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 on when to use this tool versus alternatives like docker_restart or docker_compose_up. It doesn't mention prerequisites (e.g., compose file presence), when not to use it, or scenarios where other tools would be more appropriate.

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