docs(rpc): add DESCRIPTION to F3 RPC methods

[LesnyRumcajs]

Summary of changes

Changes introduced in this pull request:

• added descs to F3 RPCs

Reference issue to close (if applicable)

Part of #6460

Other information and links

Change checklist

• I have performed a self-review of my own code,
• I have made corresponding changes to the documentation. All new code adheres to the team's documentation standards,
• I have added tests that prove my fix is effective or that my feature works (if possible),
• I have made sure the CHANGELOG is up-to-date. All user-facing changes should be reflected in this document.

Outside contributions

• I have read and agree to the CONTRIBUTING document.
• I have read and agree to the AI Policy document. I understand that failure to comply with the guidelines will lead to rejection of the pull request.

Summary by CodeRabbit

• Documentation
  • Added human-readable descriptions to F3 RPC methods, enhancing clarity for users accessing RPC documentation.

[coderabbitai]

Walkthrough

Adds DESCRIPTION: Option<&'static str> metadata fields to all 20 F3-related RpcMethod implementations in src/rpc/methods/f3.rs. No method names, permissions, request/response types, or control flow are modified.

Changes

F3 RPC Method Descriptions

Layer / File(s)	Summary
DESCRIPTION fields across all F3 RPC methods src/rpc/methods/f3.rs	Adds DESCRIPTION constant fields to all 20 RpcMethod implementations covering F3.* and Filecoin.F3* methods. No logic, types, or permissions are changed.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related issues

• Add DESCRIPTION to all RPC methods #6460: This PR directly implements the DESCRIPTION field additions for the ~20 F3 RPC methods in f3.rs that were identified as missing in that issue.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'docs(rpc): add DESCRIPTION to F3 RPC methods' clearly and accurately describes the main change: adding DESCRIPTION fields to F3 RPC methods as documentation improvements.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch f3-rpc-descs

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch f3-rpc-descs

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 64.37%. Comparing base (17098fb) to head (52ea09b).
⚠️ Report is 4 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

Files with missing lines	Coverage Δ
src/rpc/methods/f3.rs	0.00% <ø> (ø)

... and 15 files with indirect coverage changes

---

Continue to review full report in Codecov by Harness.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 17098fb...52ea09b. Read the comment docs.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.