A municipal grants coordinator must spawn research subagents during a funding-scan workflow. What configuration is required for that invocation path?
Select an answer to reveal the explanation.
Short Explanation
No Task tool on the belt means no subagent dispatch—period. Put Task in allowedTools or the grants coordinator is all talk and no scouts.
Full Explanation
A municipal grants coordinator that must spawn research subagents during a funding-scan workflow requires Task to be included in allowedTools so the coordinator can invoke those subagents. Tool allowlists are hard capability gates: without Task, or the platform's equivalent spawn tool, the coordinator literally cannot create specialists no matter what the system prompt claims about delegation.
Including Task works because permissions and prompts must align. Civic grants research that plans to fan out eligibility, compliance, and budget specialists needs the spawn tool authorized in the same configuration that describes those roles and the funding-scan objectives.
Removing all tools so subagents supposedly launch from prose instructions alone fails because prose cannot substitute for a missing spawn tool. Replacing Task with Bash-only permissions may allow scripts but does not provide the subagent invocation path the architecture question is testing. Relying on MCP resources instead of Task to spawn subagents confuses data resources with agent-spawn control flow; resources do not create research subagents.
Exam caveat: even with Task allowed, each subagent still needs its own tool restrictions via AgentDefinition or equivalent—do not confuse coordinator spawn rights with unrestricted child tools. Operational check: attempt a Task call with Task omitted from allowedTools and confirm failure; add Task and confirm a subagent spawns with the intended grants-research prompt.