supervisor_restart_addon

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It only states 'stop + start' but fails to describe what happens during the restart (e.g., process termination, state loss, configuration re-read). This is insufficient for a safe operation.

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 with a single sentence that front-loads the core purpose. Every word adds value, with no fluff.

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 simplicity of the tool (1 param), the description is minimal but incomplete. It does not mention that the 'slug' parameter is required, nor does it provide any context about the return value or confirmation of success, despite the existence of an output schema.

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 has one required parameter 'slug' with no description, and the description does not elaborate on what values are valid or how to find the slug. Schema coverage is 0%, so the description should compensate, but it adds no information about the parameter.

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 an add-on (stop + start)' clearly states the action (restart) and the resource (add-on). It distinguishes itself from sibling tools like supervisor_start_addon and supervisor_stop_addon by combining both actions.

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 usage when you want to restart an add-on in one atomic operation, but it does not provide explicit guidance on when to use this versus manually stopping then starting, nor does it mention any prerequisites or side effects.

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