# R017 Plan Review — Step 7: Replace duplicate prose

Decision: APPROVE

I re-read `PROMPT.md`, the revised `STATUS.md`, and spot-checked the files Step 7 will touch. The plan now addresses the blocker from R016: it explicitly includes the stale landing-page catalog count/prose in `web/layouts/index.html` (`~25 MCP tools`) rather than only looking for old hardcoded chip spans.

The planned scope is appropriate for Step 7:

- Replace the hand-maintained README tool list under `## MCP tool catalog` with a short paragraph and the canonical `https://icuvisor.app/reference/tools/` link, while preserving the following MCP resources/prompts and configuration sections.
- Keep landing-page tool chips rendered from the generated data source and remove or generate any remaining catalog counts so the page cannot drift from `web/data/tools.json`.
- Update `web/README.md` to document that `web/data/tools.json` is generated by `make docs-tools` / `cmd/gendocs` and should not be edited manually.

Implementation notes:

- Prefer avoiding numeric claims on the landing page unless they are derived from `site.Data.tools`; the current generated catalog has 40 entries, so any fixed count will immediately be stale-prone.
- Do not broaden this step into README slimming beyond the tool-list replacement; TP-054 owns the broader README cleanup.
- No extra changelog update is required unless the implementation adds a separate user-visible documentation change beyond the generated-catalog/source-of-truth change already recorded in Step 6.
