Scrum Master Role with Product Backlog

I've had a couple of intense discussions the last couple of days regarding the Scrum Master's role in managing the Product Backlog. During a Sprint Planning session, it was discovered that the backlog did not contain enough work for the development team for a 2 week sprint. During the planning session with the development team, a discussion started on what role the Scrum Master should take in ensuring that the Product Backlog was always detailed enough to provide enough work to fill a sprint. My stance was that the backlog is owned by the Product Owner and the Scrum Master should not have to spend time reviewing the backlog prior to the Sprint Planning in order to ensure it was ready or could become ready during the session. The planning session is time for the team to discuss the backlog and ask questions in order to gain enough details to provide an estimate and potentially accept the work for a Sprint. If the backlog is not ready and/or the Product Owner doesn't have the information the team needs during the planning session, then the team should not proceed. Some view this as the responsibility of the Scrum Master to remove the "impediment" of an inadequate backlog prior to holding the planning session. I disagree and would appreciate your thoughts on the subject.

Staff Book Club

I have started a book club for myself and my staff. We are meeting through lunch twice a week and reviewing a chapter each day. We rotate the facilitation of the meeting and chapter review among the members. We chose The 17 Indisputable Laws of Teamwork: Embrace Them and Empower Your Team in order to improve our teamwork as we have started utilizing Scrum for our projects. We just started this week, so I'll keep you posted as to the outcome.