const DESCRIPTION_WITHOUT_REVIEW: &str = "\
Hand the reader a document from this session's working tree, or from one of \
the project's document roots, opened in their own viewer. This tool is for \
documents - Markdown, PDF, plain text; a visual artifact - an HTML mockup, \
a PNG - goes to the browser instead: navigate to it and hand off that tab \
with `browser_hand_off`, never this tool. Use it when a \
document is the thing the reader should see - a plan, a report, a spec - \
rather than part of the conversation; a document the reader is meant to \
review goes here with `reviewable: true`, never as a path or link in \
chat. `path` is relative to the working directory, or absolute under \
one of the project's `document_roots` in `forge.toml`. Set `reviewable` \
to ask the reader for a review of it: they open it, comment on lines \
and answer, and their review is filed under the document's own scope. \
This session was spawned without the `review` MCP family, so you cannot \
read it back; the answer names the review's id and scope, which your lead \
reads with review__get. A PDF always opens read-only. **The answer is \
approve or send feedback**: feedback means revise the document, hand it \
off again, and keep handing it off until the reader approves; approval \
is the one signal to proceed, and neither may be read as the other; the \
one feedback box reaches you with either \
answer, though approve may leave it empty and send feedback may not. \
The reader is asked to open it or not, and **this call waits for them**: \
it answers when they approve, send feedback or say not now.";Expand description
What a session spawned without review reads instead, before it calls:
the hand-off works and the reader may still review, but the review is
the lead’s to read, so the plain description would promise it back. The
paragraphs it shares with DESCRIPTION change in both.