List Upscalers

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

No annotations are provided, so the description must disclose behavior. It states the operation is a list (GET), which implies a read-only action, and describes the type of data returned. However, it does not mention potential errors, authentication requirements, or whether the list is exhaustive or paginated. Minimal but acceptable for a simple list.

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 efficiently communicates the purpose and return content. It includes the API endpoint without unnecessary exposition, making it highly concise and well-structured.

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 simple, parameterless list tool with no output schema, the description adequately covers the tool's purpose and expected return data (model name, path, scale). It could be slightly more explicit about the scope (e.g., all upscalers vs. currently loaded), but the information is sufficient for a basic understanding.

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 tool has zero parameters, so there is no parameter information to add. The baseline of 4 applies, and the description does not introduce any confusing parameter-related content.

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 the tool's action ('List available upscalers') and specifies the returned attributes (model name, path, scale). It distinguishes itself from sibling list tools by its specific resource (upscalers) and includes the API endpoint for further clarity.

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 when to use the tool (when you need to know available upscalers) but does not explicitly mention alternatives or exclusions. Given the many sibling list_* tools, this could benefit from stating 'use this for upscaler info' vs other list tools, but the name and description are clear enough for basic usage.

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