sonarr_shutdown_sonarr

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

The annotation already indicates readOnlyHint=false and destructiveHint=false, and the description adds a redundant WRITE warning. No additional behavioral traits (e.g., impact on ongoing tasks, need to restart) are disclosed, so it adds minimal value beyond the structured metadata.

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 two short sentences that immediately convey the main action and a safety warning. Every word earns its place, with no superfluous content.

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 service action, the description is sufficient to understand the intent. It benefits from an output schema (even if empty) and clear annotations. While it could mention that a subsequent restart may be needed, the available context makes it adequately complete.

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, so the description does not need to clarify parameter usage. The baseline for zero-parameter tools is 4, and the description appropriately omits any parameter details since none exist.

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 with a specific verb and resource: 'Shut down the Sonarr service.' It is distinct from sibling tools like restart_sonarr, and the WRITE annotation adds clarity about the operation's nature.

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 such as restart_sonarr. It does not mention circumstances, prerequisites, or scenarios where shutdown is appropriate, leaving the agent without direction on tool selection.

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