Update docstring and prevent name collisions

[sjrl]

Related Issues

• fixes #issue-number

Proposed Changes:

• Update formatting of the docstring
• Pass the correct prepared data to the tracer (following what's done for the normal Pipeline)
• Get rid of "shadows from outer scope" warnings, where we reuse the same variable names in an outer scope within a function that has the potential to cause unexpected behavior. It looks in this case it was fine, but best to avoid.

How did you test it?

Notes for the reviewer

Checklist

• I have read the contributors guidelines and the code of conduct
• I have updated the related issue with new insights and changes
• I added unit tests and updated the docstrings
• I've used one of the conventional commit types for my PR title: fix:, feat:, build:, chore:, ci:, docs:, style:, refactor:, perf:, test: and added ! in case the PR includes breaking changes.
• I documented my code
• I ran pre-commit hooks and fixed any issue

[coveralls]

Pull Request Test Coverage Report for Build 13967377660

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 90.113%

---

Totals
Change from base Build 13964579599:	0.0%
Covered Lines:	9816
Relevant Lines:	10893

---

💛 - Coveralls

[davidsbatista]

I see often"shadows from outer scope" in other sections of the codebase - not top priority, but if we plan to change them all, maybe we can add a rule to ruff to detect it.

I investigated it, it seems it's still not supported but listed as something to be added as redefined-outer-name / W0621
check: astral-sh/ruff#970

we can add it to pylint though.

[davidsbatista]

looks good to me!