What a Unity Sprite Sheet Needs
Unity does not read a sprite sheet by magic. It reads a texture and a set of sprite rectangles, and when those rectangles are wrong the animation plays cropped, offset, or visibly torn at the edges. The bug is easy to miss in stills and obvious the moment the character moves on screen.
A uniform grid works only when every frame is exactly the same size, and real character art often is not. An attack frame may be wider than an idle frame, so a uniform grid clips the swinging weapon and part of the arm. Padding every frame up to the largest one fixes the clip but wastes atlas space.
A manifest records every frame as an absolute rectangle, so Unity can use those values directly and a wider pose still lands inside its own cell. Each entry also lists the frame size and its position in pixels, which removes the guesswork of dividing a texture by a hand-counted column count.
The manifest carries a per-state fps and a loop flag too, so you stop re-deriving timing by eye once the art reaches the engine. The descriptor remembers what the preview showed, and a teammate who imports later sees the same motion you approved rather than their own interpretation.

