novelai_upscale

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

Beyond annotations, it discloses that assets are sent to NovelAI, credits may be spent, free operations need no approval, paid or unknown prices return an approval plan, and there is no automatic retry. This is strong behavioral context, though it does not describe successful output handling.

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 short and front-loaded, with each sentence carrying useful operational information. There is no filler or repetition.

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?

With no output schema, the description should do more to explain the successful return value or where the upscaled output goes. It covers approval behavior and retries well, but leaves output completeness and some mutation details implicit.

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?

Schema coverage is 75%, so many parameters are already documented. The description adds that official fields pass through unchanged and that selected assets are bound, but it does not clarify the request object or approval flags beyond what the schema provides.

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 states a specific operation, using the "official standalone upscaler", which clearly identifies the resource and action. It does not explicitly differentiate from siblings such as novelai_augment or novelai_revise, so it falls short of a 5.

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?

It gives operational guidance around approvals and retries, but does not say when to choose this tool over alternatives like novelai_generate or novelai_augment. Usage is implied by the upscaler framing rather than explicitly scoped.

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