restart_sonarr

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

The description adds one useful behavioral fact beyond the title: the application is unreachable for a few seconds after restart. However, with no annotations, it does not disclose whether in-flight operations are interrupted, whether elevated permissions are required, or any broader side effects of restarting the application. It gives partial transparency but not the full picture.

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?

Two short sentences with no filler: the action comes first, followed by the relevant consequence. Every word earns its place.

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?

For a zero-parameter action with no output schema, the description is nearly complete: it states what the tool does and the key availability impact. It could additionally note that active operations may be interrupted, but for such a simple tool the missing detail is minor.

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 tool has zero parameters and an empty input schema, so there is no parameter information the description must add. The baseline of 4 applies because no parameter documentation is needed.

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?

States a clear, specific verb and resource: 'Restart the Sonarr application.' It is unambiguous and distinguishable from sibling tools by the unique action, though it mostly restates the tool name and does not explicitly differentiate itself from command-running tools like run_command.

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 given on when to use this tool instead of alternatives, or when not to use it. The second sentence only describes a post-condition (the app is unreachable for a few seconds) and provides no selection criteria, prerequisites, or exclusions.

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