List Control Preprocessors

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

No annotations are provided. The description 'List' implies a read-only operation and does not mention side effects, auth requirements, rate limits, or return/error behavior. Details that annotations would normally provide are absent, such as report of groups and params shape.

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?

One short sentence with a clear endpoint (GET /sdapi/v1/preprocessors). No filler or redundant restatement of the tool name.

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 is a trivial, parameterless list endpoint; no output schema is declared. The description names the resource and endpoint path. It does not describe return values, but for a simple list utility with no annotations this is acceptable. Complexity low, description sufficient.

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 contains zero properties and 100% description coverage, so the schema is complete; there are no parameters for the description to document or add contextual value.

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 'list' and names the resource: control preprocessors, with qualifying detail: 'with groups and configurable params'. It is clear but does not explicitly distinguish it from sibling list tools such as sdnext_list_tools or sdnext_list_samplers; however the target resource name makes the tool's purpose evident.

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 implies usage: when you need a list of control preprocessors. However, it provides no explicit guidance about when to prefer this over related listing tools, and no exclusions or alternative named.

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