Complexity, Usability and Readability of FluentAPIs - Sample: FluentMethodInvoker
    new MethodExecuter()
        .ForAllInvocationsCheckCondition(!Context.WannaShutDown)
            .When(shouldRun).ThenInvoke(x => x.Methods(new Action[] { B.Process, A.Process }))
            .When(shouldRun).ThenInvoke(x => x.Method(B.Process).Repeat(100))
            .Invoke(x => x.Method(C.Process));

I deliberately do not say anything about what this API does. I did show this API my team mates and they did not like it. For them it is unreadable.

My intention with this question is what do you think about the API, what tips do you have, what do you think about complexitiy, usability and readability of fluent APIs and how to achieve good APIs?
Complexity, Usability and Readability of FluentAPIs - Sample: FluentMethodInvoker
===

    new MethodExecuter()
        .ForAllInvocationsCheckCondition(!Context.WannaShutDown)
            .When(shouldRun).ThenInvoke(x => x.Methods(new Action[] { B.Process, A.Process }))
            .When(shouldRun).ThenInvoke(x => x.Method(B.Process).Repeat(100))
            .Invoke(x => x.Method(C.Process));

I deliberately do not say anything about what this API does. I did show this API my team mates and they did not like it. For them it is unreadable.

My intention with this question is what do you think about the API, what tips do you have, what do you think about complexitiy, usability and readability of fluent APIs and how to achieve good APIs?