Each tool targets a distinct phase of the LLM pipeline: analyze_prompt handles user/agent input, check_tool_call inspects outbound tool invocations, check_tool_result inspects inbound tool outputs, and zn_status reports configuration. There is no meaningful overlap in purpose or timing, so an agent can select unambiguously.

All names use snake_case and are readable, with check_tool_call/check_tool_result forming a clean parallel pair. The minor deviations are analyze_prompt using a different verb and zn_status using no verb at all, but the convention is still largely predictable.

Four tools is exactly right for a security gate covering the three inspection checkpoints plus a status probe. Nothing is redundant and nothing feels padded or missing.

The surface covers the full lifecycle of a security gate: pre-prompt analysis, pre-execution tool call checking, post-execution result checking, and introspection via zn_status. No obvious operational gap remains for the stated domain.