Each tool targets a distinct operation: claim verification, injection detection, antibody storage, store statistics, and demos. The only mild adjacency is between trust_check_injection (which uses learned antibodies) and trust_add_antibody (which creates them), but the action boundaries are clear from the descriptions.

All names use snake_case with a uniform `trust_` prefix, and the core tools follow a verb_noun pattern (trust_verify_claims, trust_check_injection, trust_add_antibody). trust_stats and trust_demo drop the verb, a minor deviation but still readable and predictable.

Five tools is well within the ideal range for a focused trust/verification server, and each earns its place in the workflow (check, verify, learn, inspect, demo). No obvious padding beyond the demo tool.

The antibody store has create (add) and aggregate stats but no listing/querying of individual antibodies, no delete or deactivate/expire operation, which are notable gaps for managing a learned-signature store. Verification and injection paths are otherwise complete enough for core workflows.