The read by id overlap is the clearest part of the comparison. A users/{id} template says where a record lives, while a get_user tool says to call a function, and that difference in semantics matters even when the bytes returned are the same. The warning that a resource handler with side effects breaks the expected contract is also a useful guardrail, since it keeps the read only promise honest.
OneLifeVibe
The read by id overlap is the clearest part of the comparison. A users/{id} template says where a record lives, while a get_user tool says to call a function, and that difference in semantics matters even when the bytes returned are the same. The warning that a resource handler with side effects breaks the expected contract is also a useful guardrail, since it keeps the read only promise honest.