radarr_shutdown_radarr

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

The annotation readOnlyHint=false already indicates this is a write operation. The description adds 'WRITE: this modifies your Radarr instance,' which reaffirms the mutation but does not add substantial new behavior beyond what annotations convey. It lacks details on side effects beyond the service stop, but the bar is lower with annotations provided.

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 a single, concise sentence that is front-loaded with the primary action and includes a brief note on write behavior. No unnecessary words.

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 (no parameters) and the presence of an output schema, the description is sufficient. It clearly communicates the action and side effect. It does not detail consequences of shutdown (e.g., stopping ongoing tasks), but that is not essential for a shutdown command.

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 no parameters, so the description need not explain parameters. Baseline for 0 params is 4, and nothing in the description detracts from this.

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: 'Shut down the Radarr service.' The verb 'shut down' is specific and the resource is clear. This distinguishes it from siblings like restart or ping.

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 a clear context of performing a shutdown, but it does not explicitly state when to use this tool versus alternatives like restart or stop. There is no mention of prerequisites or exclusions. The guidance is implied rather than explicit.

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