The three tools have clearly distinct purposes: resolving a site manifest, invoking a declared action, and looking up agent status. An agent can easily choose between discovery, execution, and identity lookup without overlap.

All names use snake_case and are readable, but the prefixes differ in style: gateway_resolve and gateway_invoke share a gateway_ action pattern, while kya_status uses an acronym-plus-noun pattern. This is a minor deviation rather than a confusing inconsistency.

Three tools is well-scoped for a focused gateway server: resolve, invoke, and status lookup each cover a distinct part of the workflow. There is no obvious tool bloat or trivial single-tool surface.

The core resolve-then-invoke workflow is covered, and status lookup supports agent identity checks. However, the agent lifecycle is notably incomplete: there is no way to list registered agents, register a new agent, or update agent details, which may cause dead ends for administrative tasks.