debug info
A structured response parameter that allows LLMs to report confusing or underspecified requirements back to the developer; functions as a to-do list for prompt improvements
As defined in State-Of-The-Art Prompting For AI Agents
Where it comes up · 1
Most important claims · 5 of 5Search all claims for “debug info” →
- YC internal work with agents developed an alternative escape hatch approach: giving the LLM a 'debug_info' parameter in the response format that allows it to complain to the developer about confusing or underspecified information, and this debug_info becomes a to-do list for the agent developer to fix.State-Of-The-Art Prompting For AI Agents
- YC has developed an alternative escape hatch mechanism: including a 'debug_info' parameter in response format that allows LLMs to report confusing or underspecified information directly back to the developer, creating a prioritized to-do list of prompt improvements.State-Of-The-Art Prompting For AI Agents
- Gemini 2.5 Pro's ability to reason about exceptions to rubrics is valuable for investor evaluation because some investors might be slow to respond but have great track records, and a rigid rubric would penalize them when they deserve a 91 instead of 89.State-Of-The-Art Prompting For AI Agents
- Some investors like Benchmark or Thrive have immaculate processes, respond quickly, and never ghost—making them obvious 'take their money' cases—while others are overwhelmed and slow but have strong track records, creating legitimate edge cases where debug info matters.State-Of-The-Art Prompting For AI Agents
- The debug_info parameter output from LLM evaluations (with scores like 91 vs 89) is often the most interesting and useful part, revealing nuanced reasoning about edge cases that the rubric alone wouldn't capture.State-Of-The-Art Prompting For AI Agents