The three tools map to clearly separate resources: short links, custom domains, and server/user info, so there is little risk of choosing the wrong one. The only residual ambiguity is inside each tool, where the action parameter selects among list/create/update/delete/stats, so an agent must read the enum rather than the tool name alone.

All three tools follow a uniform kutt_<resource> convention with plural noun resources (kutt_links, kutt_domains, kutt_info). There is no mixing of casing or verb styles, and the sub-actions are consistently expressed through an action parameter instead of proliferating verb-prefixed names.

Three tools is on the thin side but is justified here because each aggregates a whole CRUD surface via an action dispatcher, keeping the surface compact rather than fragmenting into a dozen verb tools. It sits at the low end of the comfortable range, which is acceptable but leaves little granularity.

Links cover list/create/update/delete/stats and domains cover list/create/delete, plus health and authenticated profile reads, which matches the core Kutt workflow. The explicit absence of a single-link GET and the lack of domain update/verification or user-profile update are minor gaps an agent can work around.