docs(extension-tools): clarify group mute operator hints

[CookSleep]

Summary

• 收紧 GroupMuteTool 的描述文本，去掉过长的参数说明块
• 明确 operatorUserId 的说明文案，补充模型自主操作、用户要求别人禁言、用户要求禁言自己等场景提示

Verification

• 未运行额外构建，属于单文件说明文案调整

[coderabbitai]

Warning

Rate limit exceeded

@CookSleep has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 11 minutes and 1 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 11 minutes and 1 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 48538072-7595-49fb-88a9-f58c6e335662

📥 Commits

Reviewing files that changed from the base of the PR and between 086a1f7 and cab921c.

📒 Files selected for processing (1)

• packages/extension-tools/src/plugins/group.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Code Review

This pull request updates the GroupMuteTool by refining the Zod schema descriptions for its parameters and simplifying the class-level description. The feedback highlights a discrepancy where the "minimum 1 second" constraint was removed from the documentation despite still being enforced in the code, and it suggests making the operatorUserId field mandatory or providing a default value to prevent potential runtime errors when the field is omitted.