Rd Stop Backend

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

No annotations are provided, so the description carries the full behavioral burden. It discloses one extra side effect, closing the console window loop, but does not warn that shutting down the backend will make subsequent rd_* calls fail until it is restarted. This is a meaningful omission for a terminating action.

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 with the core action front-loaded and no filler. The parenthetical adds useful behavioral detail without bloating the text.

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 control operation with an output schema, the description is mostly complete. The main missing context is the broader impact on other Retro Diffusion tools, but the sibling rd_start_backend makes the recovery path obvious.

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 is empty with zero parameters, so there are no parameter semantics for the description to add. Per the rubric, the zero-parameter baseline of 4 applies.

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 names a specific resource (the Retro Diffusion backend) and a specific action (shut down), and adds the concrete detail that it also closes the console window loop. This clearly distinguishes it from siblings like rd_start_backend and rd_status.

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 phrase 'ask the Retro Diffusion backend to shut down' gives a clear context for when to invoke the tool. It does not explicitly name alternatives or when-not-to-use cases, such as using rd_status to check state instead, but the purpose is self-evident enough.

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