acsmcp_call is the sole execution tool while acsmcp_methods and acsmcp_guide are both documentation/discovery tools, which creates mild overlap between listing methods and returning argument recipes. The descriptions do differentiate them well enough that an agent can pick correctly in most cases.

All three names share the acsmcp_ prefix and snake_case style, which is predictable. The only deviation is that 'call' is a verb while 'methods' and 'guide' are nouns, a minor inconsistency in an otherwise coherent scheme.

This is a facade/dispatcher design where nearly all real capability is folded into a single acsmcp_call tool, leaving two of three tools as documentation. Three tools is thin but defensible for a single-domain game automation server, sitting at the borderline of the appropriate range.

The call tool claims observation, high-level helpers, native UI, and input fallback, suggesting broad operational coverage, and the methods/guide tools provide discoverability. However, the actual surface is opaque from the outside—no explicit lifecycle operations (save/load, session state, cancellation) are visible, so gaps cannot be ruled out.