The two tools have mostly distinct roles: web_to_readable fetches and converts a URL, while read_exported_article re-reads already exported content without making a network request. There is some potential confusion because both can return Markdown content, but the descriptions clarify when each should be used based on whether the article has already been exported.

Both names use snake_case, but the patterns differ: read_exported_article follows a verb_noun form, while web_to_readable is a descriptive noun phrase rather than an action-oriented name. The names are still readable, but the set does not follow a consistent convention.

Two tools are sufficient for a focused web-to-readable workflow, but the set feels thin because there is only one primary conversion tool and one auxiliary reader. Additional tools for listing or managing exported articles would make the surface feel more complete without bloating it.

The core lifecycle is covered: fetch a URL, extract readable content, save Markdown/JSON/HTML/images, optionally generate PDF, and re-read exported content with pagination. Minor gaps remain around discovering or listing previously exported articles, but common agent workflows can be completed with the existing tools.