what does hook_field_is_empty actually mean?
I think it's used for fields that can accept multiple values, to determine whether or not the last item in the list has been filled out, or is in the 'new' state without having been filled out.

If this function didn't exist the field API wouldn't be able to make a distinction between what is classed as a filled-in row, and what is a 'New' row that hasn't been filled out, and for which the values should not be saved.

It can also be used to ensure that a minimum of columns in a field are filled out before it's classed as a save-able value.

If I remember rightly the hook is 'required' for modules that provide a field, so I'm not sure if you'll get away with leaving it out.

You could easily just implement it and return a TRUE or FALSE though for testing purposes.