A housing team discovers Agent Store already offers an agent that drafts plain-language resident letters. What should the team avoid?

When Agent Store already offers an agent that drafts plain-language resident letters, the team should avoid creating a redundant custom agent for that same purpose. The problem is unnecessary duplication: building a second agent to do the Store agent’s job repeats an existing capability rather than addressing a need. Testing the Store agent on sample resident letters before rollout is not something to avoid; it checks how the agent performs before the team uses it. Confirming the Store agent’s purpose before deciding whether a custom agent is needed is also sound, because the team should understand what the existing agent does before making that decision. Adopting the Store agent when it already meets the letter-drafting need is the appropriate choice, not the failure to avoid. Exam caveat: Avoiding a redundant custom agent does not mean the team must adopt the Store agent without first confirming its purpose and testing it; the question concerns duplication when the Store option already meets the stated need. Practical check: Confirm that the Store agent’s purpose is plain-language resident-letter drafting, test it on sample resident letters, and adopt it if it meets that need; avoid creating a custom agent that duplicates the same purpose.