BlockVectra Docs: Robinhood Chain & EVM

The two tools have clearly distinct purposes: search_docs locates pages by keyword while read_doc fetches a known path's Markdown. Descriptions explicitly cross-reference each other and explain when to use which, leaving no ambiguity.

Both names follow a verb_noun snake_case pattern (read_doc, search_docs). The only minor blemish is singular 'doc' versus plural 'docs', which is a small cosmetic inconsistency rather than a structural one.

Two tools is thin in absolute terms, but the docs-lookup domain genuinely only requires a search primitive and a fetch primitive, so each tool earns its place. Nothing redundant is present and there's no obvious omitted third operation.

Search plus read covers the core discover-then-retrieve lifecycle for documentation, including language and limit parameters. The only gap is the absence of a list/index or language-enumeration tool, which the description partially mitigates by suggesting a 'quickstart' fallback path.