Rd Neural Detail

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states that it adds/removes detail, but does not specify whether the image is modified in place, if a backend is required, what the return value is, or any side effects. This is inadequate for a complex tool.

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 front-loads the core purpose. It avoids unnecessary words, though its brevity sacrifices important contextual information.

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?

The tool has 24 parameters and no output schema, yet the description covers only the core function and one parameter. It omits essential details about configuration, expected output, dependencies on the backend, and how it differs from other neural operations. This is highly incomplete for an agent to invoke it correctly.

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?

Schema description coverage is 0%, so the description must compensate for the undocumented parameters. It only explains the 'detail' parameter (with a range), while the other 23 parameters (loras, adherence, cfg_scale, etc.) remain unexplained in both the schema and description, leaving the agent guessing.

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 tool's purpose: to add or remove detail (0-100) on existing pixel art. It names the specific action (add/remove), the resource (existing pixel art), and the key parameter with its range, distinguishing it from sibling neural tools like pixelate or resize.

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?

No guidance is given on when to use this tool versus alternatives such as rd_neural_pixelate or rd_img2img. It does not mention any conditions, prerequisites (e.g., backend running), or exclusions, leaving the agent to infer the appropriate context.

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