Each tool targets a clearly distinct resource and action: balance lookup, single-transaction status lookup by ID, and PIX charge creation. There is no plausible overlap that would cause misselection, and descriptions reinforce the boundaries (e.g. criar_cobranca_pix explicitly tells the agent to prefer webhooks over polling consultar_transacao).

All three names follow a consistent Portuguese verb_noun pattern (consultar_saldo, consultar_transacao, criar_cobranca_pix) in snake_case with no mixed conventions. The vocabulary (consultar for reads, criar for writes) is predictable and readable.

Three tools is lean but each earns its place for a narrow PIX cash-in integration, covering the core read-balance, read-status, and create-charge flows. It sits at the thin end of the acceptable range, since a payments API surface would typically warrant a few more operations.

Core cash-in lifecycle is covered (create charge, check status, check balance), but there are notable gaps: no transaction listing/history, no cancel or refund operation, and no webhook registration or management tool despite webhooks being the recommended confirmation path. Agents hitting those needs would have no tool to call.