List Masking Options

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

No annotations are provided, so the description carries the full burden. The verb 'List' and the included HTTP method (GET) clearly indicate a non-destructive read operation, which is adequate for a simple listing tool. It adds the endpoint detail beyond mere operation semantics.

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?

A single sentence that is front-loaded with the action and includes the endpoint. Every word earns its place with zero redundancy.

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 listing tool with no output schema, the description fully covers what the tool does and what it returns (models, color maps, params, types). It is as complete as needed for an agent to invoke it without further detail.

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?

There are no parameters, so the baseline of 4 applies. The description correctly implies no inputs are needed and lists the returned categories, which adds meaning to the empty 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 explicitly states 'List segmentation mask models, color maps, params and types', which is a specific verb and resource, and clearly differentiates from other list_* tools by naming the masking domain. It also includes the API endpoint for precision.

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?

Usage is implicitly clear: it's a read-only list operation for masking resources with no parameters, so the agent knows when to call it. It doesn't explicitly mention alternatives, but the resource specificity is sufficient to distinguish it from other list tools like sdnext_list_controlnets or sdnext_list_samplers.

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