What are the characteristics of a Business Requirement?
This is the main attribute a requirement must have. Think to an atom like it is one of the smallest part of an undivided matter. The requirement should be in its smallest indivisible form, containing the capability requested by the stakeholder. If it's the last piece that cannot be divided, then that is your hint that the 'Atomic' attribute is present.
Just prepare for the 'just enough' information but be sure that there is "no pathway to right or left" as I like to call it. In this way, every team member or any stakeholder understands what the Product Owner wants to achieve. Why is this important? Because in a business environment which is aimed at being Agile, transparency is essential.
There should be tests written by the quality engineers in order to ensure that the system is running having the right parameters at the right value. This way, everyone who comes into contact with the requirement understands its purpose and how the system is verified to achieve the goal.
Bonus: Necessary. Is it really needed?
Are you as a Product Owner sure that it is really needed and it is efficient to be treated now?
If you ask any stakeholder, every requirement will probably be “necessary”. The best way to verify that requirements are necessary is to 'take the light' (as I like to call it) from real customers and try to understands their 'why'....even if they say that it's necessary still can have an inexplicable 'why'.
Some (final) thoughts
What's the downsize of not having a good written requirement? Simple said: inefficiency, which can translate into losing time/money or even going out of business because of not achieving the settled goals.
This article is part of a bigger topic called Agile Software Development.