radarr_restart_radarr

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

Annotations already indicate readOnlyHint=false. The description adds 'WRITE: this modifies your Radarr instance', which essentially restates the annotation rather than providing new behavioral details such as downtime, response timing, or side effects. There is no contradiction between description and annotations.

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 one sentence with a clear verb and object, plus a brief WRITE warning. Every word earns its place; it is front-loaded and efficient.

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 simple restart operation with zero parameters and an output schema present, the description is sufficient. It clearly identifies the action and the write nature. However, it could optionally mention that restart may cause a brief interruption, but that is not critical given the sibling context and annotations.

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 no parameters, so the schema fully covers the input space. The description does not need to add parameter semantics. The 'WRITE' note does not relate to parameters but to operation type. With zero params, the baseline is high and the description does not introduce confusion.

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 uses the specific verb 'Restart' and names the resource 'the Radarr service', making the tool's action unambiguous. It also adds the explicit note 'WRITE: this modifies your Radarr instance', which reinforces the non-read-only nature and helps distinguish it from read-only list or get tools.

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 gives no guidance on when to use restart versus related tools like shutdown (radarr_shutdown_radarr) or ping. It does not mention typical scenarios (e.g., after configuration changes) or exclusions. Thus the usage context is implied only by the verb.

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