List IP Adapters

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

The description does not disclose any side effects, read-only nature, or potential caching/network behavior. Since it's a GET request, it is likely read-only, but that is not stated. No behavioral details are provided.

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 includes the endpoint. It is well-structured with no redundant words, achieving high clarity with minimal length.

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 simple and the description is sufficient for its purpose. No output schema is provided, so no return value explanation is needed. It is complete for a basic listing operation, though minor details like potential error behavior are omitted.

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 is empty (no parameters), so the description does not need to explain any parameters. It is complete in that regard, adding no unnecessary information beyond the schema.

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 list available IP adapter models, with the endpoint provided. The verb 'List' and resource 'IP adapter models' are specific and unambiguous, distinguishing it from other list tools.

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 explicit guidance is given on when to use this tool versus alternatives like other list tools. However, the tool name and description are self-explanatory for users needing IP adapter information, so it is adequate but not explicit.

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