Name the Public API Consistently
Pick one verb per concept and one casing scheme, then hold them across the whole surface. Mixed get/fetch/load, mixed delete/remove, or mixed camelCase/snake_case forces the developer to memorize each name instead of guessing it. Consistency is what makes an API learnable. For an agent-facing surface, also prefer a specific name over a generic one: displayName, slug, and externalId each carry a single meaning, whereas a bare name invites an agent to hallucinate what it holds and use it inconsistently from one call to the next.
Incorrect (three verbs for one concept, mixed casing):
client.getUser(id);
client.fetchPosts(userId);
client.load_comments(postId);
client.removeUser(id);
client.deletePost(postId);Correct (one verb per concept, one casing scheme):
client.getUser(id);
client.getPosts(userId);
client.getComments(postId);
client.deleteUser(id);
client.deletePost(postId);