Report a bug, confusion, bad documentation, or improvement idea.

Call this when you:

• had to guess or weren't confident in your output

• hit a missing tool or capability

• found unclear, wrong, or incomplete tool documentation

• encountered ambiguous instructions

• want to suggest a new tool, workflow step, or prompt fix

Non-blocking — log and continue your task. No response expected. There is no penalty for logging; silence is the failure mode.

description: what went wrong or what you'd like improved (max 200 chars) severity: low (friction) | medium (had to guess/workaround) | high (abandoned/wrong output) section: which instruction or tool caused the issue (max 80 chars) mode: ambiguous_instruction | missing_tool | bad_tool_doc | hallucination_risk | wrong_scope | memory_miss | other