Ase Rotate Sprite

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does add the angle/direction constraints and the target scope, but it fails to disclose that this is an in-place mutation (rotating the sprite/layer directly), whether the change is destructive or undoable, whether it affects only the current frame or the whole animation, and what the side effects are. With zero annotation coverage, this is a significant gap for a mutation tool.

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?

One tight sentence with zero filler. The verb and critical angle constraint are front-loaded, and every word earns its place. This is exactly the right size for a simple operation.

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 0% schema coverage, no annotations, and the fact that this is a mutating operation, the description is under-specified. It covers the core purpose but leaves sprite_path unexplained, gives no behavioral context (in-place vs. new sprite, frame scope, destructiveness), and offers no usage guidance. The presence of an output schema does not compensate for these input-side and behavior-side gaps.

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%, so the description must compensate for the schema's bare property names. It does add meaning for 'angle' (implies 90/180/270) and 'target' (via 'sprite or active layer'), but 'sprite_path' is entirely undocumented in both the schema and the description. Partial compensation is not enough for a 0%-coverage 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 states a specific verb ('Rotate'), a specific resource ('sprite or active layer'), and precise scope ('90/180/270 degrees clockwise'). It clearly distinguishes the tool from sibling ase_flip_sprite (rotate vs. mirror) and other transforms like ase_scale_sprite, so an agent can tell what it does without opening the schema.

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?

There is no guidance on when to use this tool versus alternatives, no exclusions, and no prerequisites. The parenthetical '(sprite or active layer)' hints at the target parameter but does not explain when choosing one over the other is appropriate. Compared to the calibration example, this is bare-minimum operation description with no decision support.

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