Which two criteria are useful in deciding if something should be documented every sprint?

if the documentation is adding to the quality and maintenance of the software this is definitely a good argument for documenting every sprint. Just because that's the way it's done and we don't want change is not a good reason. Tooling that requires is also isn't. And the scrum master cannot demand this kind of things. If the company's definition of done says so, you must :)