restart_ui

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

No annotations are provided, so the description carries full disclosure burden. It surfaces one crucial behavioral trait—does not interrupt transcoding—which is genuinely useful. However, it omits other expected side effects of a restart, such as brief UI downtime or session termination.

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?

A single focused sentence with the action front-loaded, the endpoint in parentheses, and the key caveat placed at the end. Every word earns its place—no padding.

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 tool with no output schema, the description sufficiently explains what happens and when to invoke it. Minor gaps include not mentioning what the caller should expect after invocation (e.g., UI downtime or recovery time), but these are not critical for a simple restart action.

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 there are no parameter semantics to clarify. The schema is 100% complete by virtue of having an empty properties object, and the description adds no necessary parameter information.

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?

Clearly states the verb 'Restart', the resource 'Tdarr web UI process', and the exact endpoint. This distinguishes it from sibling tools like restart_server or restart_node by explicitly focusing on the UI process.

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?

Gives an explicit trigger condition: 'use it when the UI is unresponsive but jobs are fine.' The clarification that it does not interrupt transcoding also implies a boundary for when not to use it, though it doesn't name alternative tools.

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