convert_document performs conversion while estimate_savings reports token/cost comparisons; the two purposes are entirely non-overlapping. An agent can never confuse 'do the conversion' with 'measure the benefit of the conversion'.

Both names follow a clean snake_case verb_noun pattern (convert_document, estimate_savings) with concrete, descriptive objects. No mixed conventions or vague verbs.

Two tools is thin but defensible for a narrowly scoped local document-to-Markdown utility with a built-in savings reporter. Still, the surface feels minimal — pagination and format handling are folded into parameters rather than exposed as tools.

The core lifecycle (convert a file, paginate with next_cursor, quantify savings) is covered, and the savings tool sensibly complements conversion. Minor gaps: no format/support discovery, no batch conversion, and no way to inspect or resume a conversion beyond the cursor.