What to do when testers are not satisfied with the documentation written by the developers?

Question

Project management

I work for a young company and we are facing a problem.
Feature developers write technical documentation (requirements), which is subsequently used by testers during the testing process.
On the part of the testers' team lead, there is a complaint - the requirements for features are "incomprehensible", "inadequate", "incorrect" and stuff like that. He cannot formulate requirements for requirements, but he can show how they should look in his opinion. An example per function in a database is below.
Here is what the developer wrote:

For each element of array Z (an array of arrays), do the following:
- If the element has an empty subarray of placements, and the subarray of landings is not empty:
-- delete rows from table X according to these landings
- If the element has an empty subarray of landings, but the subarray of placements is not empty:
-- delete rows from table X by given placements
- If the element has non-empty subarrays of landings and placements:
-- delete rows from table X by given landings and placements

Here's how the testers' team leader wrote (as he wanted to see it):

Each element of the array Z (an array of arrays) is considered separately and does not depend on another element
In the future, we will use the name element.Z to refer to an element of the array Z
- All rows from the X table are deleted in which the landings correspond to the landings element.Z
-- Condition : No placements specified in element.Z
- Remove all rows from table X in which placements match element.Z
-- Condition: No landings specified in element.Z
- Remove all rows from table X in which landing and placement are equal to landing and a placement obtained by combining landings with placements from element.Z
-- Condition: element.Z contains at least one landing and at least one placement

This is an example of a simple function.
So, the developer writes his vision, the testers' team leader writes his own. The tester's team lead cannot form the requirements for the requirements (i.e., in fact, the requirements written by the developer cannot be checked for "understandability" and "adequacy").
Questions:

1. Are the comments of the team leader of the testers fair?
   
2. Have you encountered such a problem, and how is it solved in your company (tech writer)?
   

Answer 1

Requirements must be written by an analyst. Or someone who understands writing requirements.
Testers should write a test plan for these requirements, consisting of test cases with full coverage of each requirement.
And you don’t have requirements, but some description of the functionality from the developers and a description of testing from the testers.
I advise you to read the ieee software requirements standards
Shl.
Yes, I completely forgot. before requirements it is necessary to describe yuz cases. and from them to get test cases.
get someone to study the requirements management documentation to get a normal design-test process.

Answer 2

1. Find out why it is impossible to maintain a normal document flow.
   For the gifted, please write a video. Silent movies are out of the question!