Rd Neural Resize

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the outcome ('keeping detail coherent'), but does not reveal whether the operation is destructive to the source, how long it might take, what output format is returned, or any side effects (e.g., writing files, requiring a backend). This is a significant gap for a tool with 23 parameters.

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 with no fluff, which is concise. However, it is so minimal that it borders on under-specification rather than elegant conciseness. It lacks structure such as sections or usage examples, and for a tool this complex, a bit more detail would be warranted. It front-loads the purpose but does not earn its place by adding utility beyond the name.

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?

Given 23 parameters, no output schema, and no annotations, the description is drastically incomplete. It does not explain what the parameters do, what the output looks like, or any caveats. An agent cannot reasonably invoke this tool correctly with only the description and schema, as the semantics of most parameters remain opaque.

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 23 parameters with 0% description coverage, meaning the schema only provides names and defaults. The description does not explain any parameter meanings, such as width, height, pixel_size, steps, or adherence. It adds zero value to parameter understanding, leaving the agent to guess what each controls.

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 core function: changing pixel density/resolution of pixel art while preserving detail. It names a specific verb ('resize') and a resource (pixel art), and the phrase 'neural' hints at the method. However, it does not differentiate from sibling tools like rd_neural_pixelate or rd_neural_detail, which also deal with pixel-art processing, so it misses the distinguishing nuance.

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 guidance is given on when to use this tool versus alternatives. It does not mention when to prefer rd_neural_resize over rd_neural_pixelate, rd_neural_detail, or ase_scale_sprite, nor does it state any prerequisites (e.g., backend running, image loaded). The agent is left to infer usage from the name and context.

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