/particle command params inconsistent

What I expected to happen was:

The /particle command should accept both parameters (Data value and metadata) for blockcrack, blockdust and fallingdust, just like for iconcrack, so the syntax for blockcrack, blockdust, fallingdust and iconcrack is

/particle <Particle name> <x y z> <dx dy dz> <velocity> [<count>] [<mode>] [<entity>] [<data value>] [<metadata>]

Examples which are expected to work
blockdust of spruce planks:

/particle blockdust ~ ~ ~ 0 0 0 1.0 100 normal @a 5 1

iconcrack of purple dye:

/particle iconcrack ~ ~ ~ 0 0 0 1.0 100 normal @a 351 5

What actually happened was:

It only accepted one parameter, which is metadata × 4096 + data_value, so the syntax for blockcrack, blockdust and fallingdust is

/particle <Particle name> <x y z> <dx dy dz> <velocity> [<count>] [<mode>] [<entity>] [<weird particle ID>]

while the syntax for iconcrack is

/particle <Particle name> <x y z> <dx dy dz> <velocity> [<count>] [<mode>] [<entity>] [<data value>] [<metadata>]

Examples which actually work
blockdust of spruce planks:

/particle blockdust ~ ~ ~ 0 0 0 1.0 100 normal @a 4101

iconcrack of purple dye:

/particle iconcrack ~ ~ ~ 0 0 0 1.0 100 normal @a 351 5

How to reproduce:

1. Try to execute the commands I provided above
2. Note that iconcrack's syntax is different than the syntax of the other particles which need parameters

About this report:

I searched for possible duplicates for a long time and didn't find any. I'm really sorry if I overlooked one and posted another duplicate report

If you want to solve this as WAI, please write a comment why it is. I do not think it is WAI. Inconsistance normally is not intended. Also, Searge wrote a while ago that it is not intended that iconcrack has two parameters while blockcrack and blockdust haven't.