This is kind of a wild take. Estimates should be reviewed like anything else on a team, and if the estimate doesn’t fit the timeline, the team should try to either split up / parallelize the work, drop scope, or look for a creative solution (usually involving taking on some strategic tech debt).
This is completely consistent with what I said. Even as a team effort, you want your manager to trust when you say something has some non-obvious complexity. And the manager wants to trust their team members.
But my comment stems from someone above who said they do the minimum amount of work possible. This sucks for the team, who is working hard and trying to make progress, meanwhile this person is barely doing any work every day in between gaming or reddit or whatever, but (presumably) still joins stand-ups and Slack to chime in with whatever "complication" he's having to work through that day, and always gives the impression that their work is super tricky.
You might be misunderstanding what "minimum amount of work" means. The OP might simply be referring the minimum amount of work achievable without overexerting oneself via extra hours, working weekends, under stress, etc. Someone's minimum amount of work can be hard work. They literally said "I will always finish my work in the time it is expected to be finished." So if that amount of time is not satisfactory, it is up to the manager to ask for the time to be shortened- and then that becomes the new minimum.
Work planning should be a team effort.