chore(core): fix comment typo

[Mapleeeeeeeeeee]

What

Fix a comment typo in packages/core/src/tools/tools.ts.

Why

Issue #14648 reported two comment typos. Upon investigation:

• occurence → occurrence in fileSearch.ts has already been fixed in the codebase
• @params → @param in tools.ts still exists and is fixed in this PR

How

Changed @params to @param in the JSDoc comment (line 420).

Notes

• Only comment change, no functional impact

Fixes #14648

[gemini-code-assist]

Summary of Changes

Hello @Mapleeeeeeeeeee, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on improving code documentation by fixing a minor typo in a JSDoc comment within the core package. The change ensures that the parameter documentation adheres to standard JSDoc syntax, enhancing readability and maintainability without introducing any functional alterations to the system.

Highlights

• Comment Typo Fix: Corrected a typo in a JSDoc comment, changing @params to @param for the abortSignal parameter in the validateBuildAndExecute method.
• Affected File: The change was made in packages/core/src/tools/tools.ts.
• Issue Addressed: This pull request addresses a specific part of Issue Fix 2 comment typos in the core package #14648, which reported multiple comment typos.
• No Functional Impact: The change is purely cosmetic, affecting only documentation, and has no impact on the functionality or behavior of the code.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request correctly fixes a typo in a JSDoc comment within packages/core/src/tools/tools.ts, changing @params to the correct @param tag. This is a good, small change that improves documentation clarity. The change is correct and has no functional impact. I have no further comments.