SmartFetch

All four tools describe essentially the same operation: fetching or extracting a webpage and returning clean text/Markdown. fetch_webpage explicitly includes browser rendering and Markdown output, so it overlaps with every other tool and leaves no clear basis for selecting among them.

Most names follow a verb-first snake_case pattern (fetch_webpage, render_webpage, extract_webpage_text), but webpage_to_markdown breaks the pattern by using a noun_to_noun form. The naming is readable but not fully consistent.

Four tools is not inherently excessive, but the set is highly redundant for a narrow fetch/extract purpose; one comprehensive tool or at most a two-tool split would be more appropriate. The current count inflates the surface without adding distinct capabilities.

The core job of fetching and converting public webpages to text/Markdown is covered, including browser rendering for JavaScript-heavy pages. However, the surface is so overlapping that it lacks meaningful capability stages or distinct output modes beyond the bundled text/Markdown/metadata payload.