Rotate sprite view

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

Annotations already declare non-read-only, non-destructive behavior. The description adds useful context: the operation invokes the model, does not rotate pixels, and never changes image_path. It still omits where generated outputs are written and whether new files are created.

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 three short sentences, front-loaded with purpose and followed by key caveats. It wastes little space, though the instruction to provide subject and view could be more tightly integrated.

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 9-parameter tool with no output schema and zero schema descriptions, the description is too sparse. It clarifies the core operation but leaves most parameters and the output behavior undocumented, so an agent cannot fully understand the call from the definition.

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 description coverage is 0% across 9 parameters, so the description must compensate. It only mentions subject, view, and image_path, leaving seed, palette, symmetry, variants, background, and output_dir completely unexplained.

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: re-viewing a sprite from a requested direction using SpriteLoom's instruction mode, and clarifies that it does not rotate pixels. It is distinguishable from generic generation, though it does not explicitly contrast with siblings such as edit_sprite or generate_sprite.

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 implied: use this when you need a new directional view of a subject, and note that it is model-based rather than pixel manipulation. However, there are no explicit exclusions, prerequisites, or named alternatives to guide selection among the sibling sprite tools.

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