Rd List Models

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

There are no annotations provided, so the description carries the burden of behavioral disclosure. The description indicates it is a read-only query, which is inferred from the verb 'List'. However, it does not disclose whether the list is cached, whether it requires a running backend, or whether it reflects the current configuration versus defaults. For a listing tool with no side effects, the inference is adequate, but more detail would help.

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 sentence that is concise and front-loaded with the action 'List' and the exact items covered. It wastes no words and conveys the scope efficiently. It is appropriately sized for a zero-parameter discoverability tool.

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?

Given the tool's simplicity (no parameters, clearly scoped list), the description is sufficient. The output schema exists, so the description does not need to explain return values. The main missing context is when to use it relative to alternatives, but the specificity of the listed item types mitigates that. For a discovery tool, the description is practically complete.

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 has zero parameters, and schema description coverage is 100% by default. The description does not add any parameter semantics because there are none. However, it does not explicitly state that no parameters are required, which could lead an agent to wonder about optional parameters. A sentence like 'Takes no arguments' would be clearer. Thus, the description adds minimal value beyond the schema in this dimension.

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 lists selectable base models, ControlNet models, texture tiling modes, and dimension presets. It distinguishes itself from sibling listing tools like rd_list_loras by specifying the exact categories of items it lists. However, it does not explicitly mention the rd_ namespace context, but that is implied by the resource names.

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 tells the agent when to use this tool: when the agent needs to know available base models, ControlNet models, texture tiling modes, or dimension presets. Since it takes no parameters, it is a discovery tool. It does not explicitly state when NOT to use it or mention alternatives, but the resource list is specific enough that confusion with other list tools is unlikely. It does not mention that this is a preliminary step, but the implication is clear for selection tasks.

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