A parks events agent should summarize approved event PDFs without wandering the open web. What capability choice is appropriate?
Select an answer to reveal the explanation.
Short Explanation
Give the parks agent the tools it needs for the PDF stack—and skip the tourist trip across the whole web. Right capabilities, right job.
Full Explanation
Enabling summarization for the event PDF knowledge while leaving unrelated web browsing off is the appropriate capability choice for a parks events agent. The task is to summarize approved event PDFs already in knowledge—permits, schedules, vendor rules—not to roam the open web. Matching capabilities to that municipal job keeps outputs on the city’s documents and reduces off-scope retrieval.
Turning on unrestricted web browsing as the only capability and ignoring the event PDFs fails because it abandons the approved corpus. The agent may summarize random third-party event pages, outdated park listings, or marketing sites instead of the city’s signed PDFs.
Disabling every capability so the agent cannot open the approved event files fails by under-scoping: without summarization (or equivalent document use), the agent cannot perform the assigned parks task even though the PDFs are present.
Replacing PDF summarization with a requirement to rewrite city charter text from memory fails conceptually and operationally. Charter rewriting is outside events scope, and memory-based rewrite invites hallucination of legal text the parks desk should never improvise.
Exam caveat: Capabilities are task-scoped tools; AB-730 expects you to enable what the municipal job needs and leave unrelated powers off rather than maximizing every switch.
Operational check: Attach or point knowledge at an approved event PDF, ask for a summary, and confirm the agent uses that file; attempt an off-topic web-style ask and verify browsing remains unavailable so the helper stays on the parks event stack.