docs: cut prose bloat from the generated tool pages The tool docstrings are written for LLM tool selection, not for a human reading a reference page, so rendering them whole padded every entry with routing ("for a count use X"), glossary definitions and advice the parameter table already gave two inches below. Each entry is now its first paragraph, then at most two notes, then the table. A note survives only where acting on the tool without knowing it produces a wrong result, a failure, or an irreversible change -- descriptive detail and when-to-use-this guidance are dropped however true they are, and most tools correctly end up with none. The generic error contract moves to the page header instead of repeating on all 200 entries. Tables and parameter notes are byte-identical; only prose was cut. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
docs: build out the wiki Add 26 pages covering setup, configuration and the full tool reference for dataverse-mcp 3.9.1, and replace the Home stub with a signpost. Twelve pages are hand-written: installation, client setup, authentication, a first-steps walkthrough, configuration, safety and permissions, tool categories, how it works, and troubleshooting, plus the sidebar and footer. Every count and error string on them was taken from a live server rather than read out of the source. The remaining fifteen -- Tool-Index and one page per category -- are generated from the tool registry by scripts/gen_wiki_tools.py in the main repo and must not be edited by hand. They cover all 200 tools across 14 categories. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>