PlainError

The three tools map to distinct intents: discovery (search_fixes), retrieval of a known page (get_fix), and diagnosis of a freshly pasted error (explain_error). There is mild overlap because explain_error also returns fix steps and may reuse published answers, but the descriptions make the 'search vs. fetch vs. explain' boundary reasonably clear.

All three names follow a clean snake_case verb_noun pattern: explain_error, get_fix, search_fixes. The singular/plural difference reflects cardinality (one page vs. many results) rather than an inconsistency in convention.

Three tools is on the lean side but is well matched to a focused error-fix lookup service; each tool covers a genuinely different entry point. Nothing feels redundant, though the surface is small enough that another operation (e.g. browsing categories/hubs) could plausibly have earned a place.

The read-only lookup lifecycle is covered end to end: find fixes, fetch full content, and explain a new error. Minor gaps exist—no way to enumerate categories or hubs (only the Windows Update hub is mentioned inside get_fix), and no feedback channel for whether a fix worked—but agents can work around these.