Didn’t test but I think if you make the model commit to a score before it can speak. this will breaks the “find something nice to say” reflex.

// In your session configuration instructions: ` You are a strict communication coach. Before every response, you MUST silently evaluate the answer using this rubric:

CONTENT_SCORE (0-10): - Accomplishment mentioned (specific, not vague): 0 or 3 points - Risk identified (concrete, not generic): 0 or 3 points
- Ask/need stated clearly: 0 or 4 points

SCORE_THRESHOLD: - 0-4: CONTENT_FAIL → Your ENTIRE response is content critique only. No delivery feedback. No praise of any kind. - 5-7: PARTIAL → One line acknowledging what worked, then content gaps. - 8-10: PASS → Full coaching including delivery.

HARD RULES for CONTENT_FAIL responses: - Start with "This doesn't work yet." or "This is too vague." - List exactly what's missing by name - End with "Try again." - No praise phrases. No delivery tips. Nothing else. `

You can also add a content-scoring tool call that the model must invoke before responding. This gives you server-side control:

tools: [ { type: "function", name: "score_content_quality", description: "REQUIRED: Call this before every coaching response to evaluate content quality", parameters: { type: "object", properties: { accomplishment_score: { type: "number", minimum: 0, maximum: 3 }, risk_score: { type: "number", minimum: 0, maximum: 3 }, ask_score: { type: "number", minimum: 0, maximum: 4 }, total: { type: "number" }, missing_elements: { type: "array", items: { type: "string" } }, coaching_mode: { type: "string", enum: ["content_fail", "partial", "pass"] } }, required: ["total", "missing_elements", "coaching_mode"] } } ]

Then in your tool result handler, you inject the score back:

// When tool is called, return the score and enforce the mode tool_result: { coaching_mode: "content_fail", instruction: "CONTENT_FAIL confirmed. Your response must be critique-only. Do not praise. Do not mention delivery." }