Rd Start Backend

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

With no annotations, the description carries the behavioral burden. It discloses headless execution, no console window, UTF-8 IO environment, and log output to mcp-backend.log. It does not describe return behavior or failure modes, but the essential operational traits are present.

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?

Two short sentences deliver the core action and the key operational details without waste. The main purpose is front-loaded, and every clause adds value.

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 startup tool, the description covers what it does, when it runs, and how it behaves headlessly. An output schema exists, so return-value documentation is not required. It could mention prerequisites or blocking behavior, but nothing critical is missing.

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 and the input schema is empty, so there is no parameter meaning to add. The description correctly avoids inventing parameters, and the baseline for zero-parameter tools is 4.

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 a specific verb ('Start') and resource ('Retro Diffusion local backend'), names the underlying file (image_server.py), and adds the condition 'if not already listening.' This clearly distinguishes it from siblings like rd_stop_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?

It states when the action is appropriate ('if not already listening'), implying idempotent startup. It does not explicitly name alternatives or exclusion cases, but the condition and sibling set make usage context reasonably clear.

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