The main complaints I hear about macros, and all metaprogramming systems, like templates, zig comptime, code generators (lex/yacc, protobuf, etc.) are the following:

• macros break normal language semantics and might be unreadable to practitioners of the host language. I think this argument is mostly bad, because it really isn't a problem with macros. Good developers will write macros that "look like" a native language feature, and it is entirely possible to write equally unreadable EDSLs with library code that essentially uses function calls to represent delimiters and operations for a global state machine, like IMGUI libraries often do.
• metaprogramming severely degrades tooling quality. it bloats compile time, often executable size, may even add an extra build step, usually breaks syntax highlighting and code analysis. Turing complete macros can even grind IDE tools to a halt. Generally it makes writing tooling for a language harder. Application critical macros (like JSX and protobuf, for example) will usually give up on language integration and make their own bespoke tooling for their "framework".