docs: Use {tooliconl} for inline paragraph tool refs

Switch {tool} → {tooliconl} in prose paragraphs across tool pages,
gotchas, and demo. Keeps {tool} (full badge) in bulleted lists,
headers, and tables per the convention in AGENTS.md.

Author: tony

docs/demo.md

@@ -66,7 +66,7 @@ These are the actual tool headings as they render on tool pages:
 
 ### In prose
 
-Use {tool}`search-panes` to find text across all panes. If you know which pane, use {tool}`capture-pane` instead. After running a command with {tool}`send-keys`, always {tool}`wait-for-text` before capturing.
+Use {tooliconl}`search-panes` to find text across all panes. If you know which pane, use {tooliconl}`capture-pane` instead. After running a command with {tooliconl}`send-keys`, always {tooliconl}`wait-for-text` before capturing.
 
 ### Dense inline (toolref, no badges)
 
@@ -83,7 +83,7 @@ The fundamental pattern: {toolref}`send-keys` → {toolref}`wait-for-text` → {
 ## Admonitions
 
 ```{tip}
-Use {tool}`search-panes` before {tool}`capture-pane` when you don't know which pane has the output you need.
+Use {tooliconl}`search-panes` before {tooliconl}`capture-pane` when you don't know which pane has the output you need.
 ```
 
 ```{warning}

docs/tools/panes.md

@@ -9,8 +9,8 @@
 after running a command, checking output, or verifying state.
 
 **Avoid when** you need to search across multiple panes at once — use
-{tool}`search-panes`. If you only need pane metadata (not content), use
-{tool}`get-pane-info`.
+{tooliconl}`search-panes`. If you only need pane metadata (not content), use
+{tooliconl}`get-pane-info`.
 
 **Side effects:** None. Readonly.
 
@@ -51,7 +51,7 @@ $
 **Use when** you need pane dimensions, PID, current working directory, or
 other metadata without reading the terminal content.
 
-**Avoid when** you need the actual text — use {tool}`capture-pane`.
+**Avoid when** you need the actual text — use {tooliconl}`capture-pane`.
 
 **Side effects:** None. Readonly.
 
@@ -97,7 +97,7 @@ Response:
 which pane has an error, finding a running process, or checking output
 without knowing which pane to look in.
 
-**Avoid when** you already know the target pane — use {tool}`capture-pane`
+**Avoid when** you already know the target pane — use {tooliconl}`capture-pane`
 directly.
 
 **Side effects:** None. Readonly.
@@ -146,7 +146,7 @@ Response:
 **Use when** you need to block until specific output appears — waiting for a
 server to start, a build to complete, or a prompt to return.
 
-**Avoid when** you can poll with {tool}`capture-pane` instead, or if the
+**Avoid when** you can poll with {tooliconl}`capture-pane` instead, or if the
 expected text may never appear (set a timeout).
 
 **Side effects:** None. Readonly. Blocks until text appears or timeout.
@@ -190,7 +190,7 @@ Response:
 terminal. This is the primary way to execute commands in tmux panes.
 
 **Avoid when** you need to run something and immediately capture the result —
-send keys first, then use {tool}`capture-pane` or {tool}`wait-for-text`.
+send keys first, then use {tooliconl}`capture-pane` or {tooliconl}`wait-for-text`.
 
 **Side effects:** Sends keystrokes to the pane. If `enter` is true (default),
 the command executes.
@@ -339,7 +339,7 @@ Response:
 **Use when** you're done with a specific terminal and want to remove it
 without affecting sibling panes.
 
-**Avoid when** you want to remove the entire window — use {tool}`kill-window`.
+**Avoid when** you want to remove the entire window — use {tooliconl}`kill-window`.
 
 **Side effects:** Destroys the pane. Not reversible.
 

docs/tools/sessions.md

@@ -8,8 +8,8 @@
 **Use when** you need session names, IDs, or attached status before deciding
 which session to target.
 
-**Avoid when** you need window or pane details — use {tool}`list-windows` or
-{tool}`list-panes` instead.
+**Avoid when** you need window or pane details — use {tooliconl}`list-windows` or
+{tooliconl}`list-panes` instead.
 
 **Side effects:** None. Readonly.
 
@@ -47,7 +47,7 @@ Response:
 **Use when** you need to verify the tmux server is running, check its PID,
 or inspect server-level state before creating sessions.
 
-**Avoid when** you only need session names — use {tool}`list-sessions`.
+**Avoid when** you only need session names — use {tooliconl}`list-sessions`.
 
 **Side effects:** None. Readonly.
 
@@ -84,7 +84,7 @@ Response:
 container — create one before creating windows or panes.
 
 **Avoid when** a session with the target name already exists — check with
-{tool}`list-sessions` first, or the command will fail.
+{tooliconl}`list-sessions` first, or the command will fail.
 
 **Side effects:** Creates a new tmux session. Attaches if `attach` is true.
 
@@ -158,7 +158,7 @@ Response:
 **Use when** you're done with a workspace and want to clean up. Kills all
 windows and panes in the session.
 
-**Avoid when** you only want to close one window — use {tool}`kill-window`.
+**Avoid when** you only want to close one window — use {tooliconl}`kill-window`.
 
 **Side effects:** Destroys the session and all its contents. Not reversible.
 
@@ -190,7 +190,7 @@ Session killed: old-workspace
 **Use when** you need to tear down the entire tmux server. This kills every
 session, window, and pane.
 
-**Avoid when** you only need to remove one session — use {tool}`kill-session`.
+**Avoid when** you only need to remove one session — use {tooliconl}`kill-session`.
 
 **Side effects:** Destroys everything. Not reversible.
 

docs/tools/windows.md

@@ -8,7 +8,7 @@
 **Use when** you need window names, indices, or layout metadata within a
 session before selecting a window to work with.
 
-**Avoid when** you need pane-level detail — use {tool}`list-panes`.
+**Avoid when** you need pane-level detail — use {tooliconl}`list-panes`.
 
 **Side effects:** None. Readonly.
 
@@ -333,7 +333,7 @@ Response:
 
 **Use when** you're done with a window and all its panes.
 
-**Avoid when** you only want to remove one pane — use {tool}`kill-pane`.
+**Avoid when** you only want to remove one pane — use {tooliconl}`kill-pane`.
 
 **Side effects:** Destroys the window and all its panes. Not reversible.
 

docs/topics/gotchas.md

@@ -6,9 +6,9 @@ Things that will bite you if you don't know about them in advance. For symptom-b
 
 ## Metadata vs. content
 
-{tool}`list-panes` and {tool}`list-windows` search **metadata** — names, IDs, current command. They do not search what is displayed in the terminal.
+{tooliconl}`list-panes` and {tooliconl}`list-windows` search **metadata** — names, IDs, current command. They do not search what is displayed in the terminal.
 
-To find text that is visible in terminals, use {tool}`search-panes`. To read what a specific pane shows, use {tool}`capture-pane`.
+To find text that is visible in terminals, use {tooliconl}`search-panes`. To read what a specific pane shows, use {tooliconl}`capture-pane`.
 
 This is the most common source of agent confusion. The server instructions already warn about this, but it bears repeating: if a user asks "which pane mentions error", the answer is `search_panes`, not `list_panes`.
 
@@ -31,7 +31,7 @@ The `enter` parameter defaults to `true`, which is correct for commands (`make t
 {"tool": "capture_pane", "arguments": {"pane_id": "%0"}}
 ```
 
-The capture above may return the terminal state **before** pytest runs. Use {tool}`wait-for-text` between them:
+The capture above may return the terminal state **before** pytest runs. Use {tooliconl}`wait-for-text` between them:
 
 ```json
 {"tool": "send_keys", "arguments": {"keys": "pytest", "pane_id": "%0"}}