bad design: parameters crossing multiple classes and methods

I m questioning myself about some code where parameters get passed through multiple methods without modifications.

for example:

method1(paramA, paramB)
call service2(paramA, paramB)
call facade3(paramA, paramB)
call service4(paramA, paramB)
call daoLayer5(paramA, paramB)

this things make me sad :( but i'm not sure if there is a way to deal with it. Or if the architecture force me to do things like this.