Flowwoods — Real-user research recruiting

Each tool maps to a distinct phase: reading provider facts (get_service_offer), computing a fee+incentive estimate (estimate_research_cost), and sending an inquiry (submit_research_brief). The only mild friction is that get_service_offer surfaces pricing while estimate_research_cost also returns cost figures, so an agent may briefly hesitate over which to call for pricing; the descriptions resolve this (scope facts vs. computed total).

All three names follow a clean verb_noun snake_case pattern: estimate_research_cost, get_service_offer, submit_research_brief. The verbs (estimate/get/submit) accurately signal the differing side-effect profiles.

Three tools match a deliberately narrow, no-transaction recruiting inquiry surface, and each earns its place. The set is on the lean side, but for a pre-sales feasibility flow that is reasonable rather than deficient.

The read → estimate → inquire path is covered, but there is no way to check the status of a submitted brief or retrieve previously submitted details, leaving an agent at a dead end after submit_research_brief. Given the explicit no-order/no-reservation stance this may be intentional, but the lifecycle stops short.