List Loaded LoRAs

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

No annotations are present, so the description bears the full burden. It discloses the read-only nature via 'GET' and the state-dependent 'currently loaded' qualifier, but does not describe return format or edge cases. This is adequate for a simple listing 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?

One concise sentence with the endpoint in parentheses. No wasted words, front-loaded verb.

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, simple listing operation, this description is sufficiently complete. It names the resource (loaded LoRA names) and the endpoint, which is all essential information given no output schema.

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, so the description correctly makes no mention of parameters. 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?

States exactly what it does: lists currently loaded LoRA names. The 'currently loaded' qualifier distinguishes it from sibling 'sdnext_list_loras' which presumably lists all available LoRAs.

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?

Provides no explicit when-to-use or alternatives, but the phrase 'currently loaded' implies it is for inspecting the active set. Does not name sibling tools like 'sdnext_list_loras' or 'sdnext_refresh_loras', so usage context is only implied.

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