To fully answer what issues may be going on, getting the full plan is going to be the best bet.

To give you some general information, an index spool is a mechanism employed by the optimizer to assist with data processing. It's not the cause of your performance problems. No performance problems come directly from an execution plan. The execution plan is the result of the query, your data structure, the constraints and the statistics available to the optimizer. Problems don't lie with the execution plan. They lie with the code, the stats and your structures. Understanding the execution plan can help you understand why your query and structures lead to poor performance, but it is not the poor performance itself. It's always back to those other objects. The plan simply defines how the query is being met.

An index spool operation can be verify beneficial. It ensures that data is accessed one time from disk and then put into a temporary index for reuse elsewhere in the query. This can result in significant cost savings versus going back to the original data set over and over again.