Fetch current Fanqie novel rankings by channel, rank type, and category. Returns book titles, authors, readers, status, and chapter counts for trend analysis.
读取最新番茄榜单（按频道/榜型/品类）。返回书名、作者、在读、状态、章节数、book_id——不含简介全文与版权图。
| Name | Required | Description | Default |
|---|---|---|---|
| top | No | 返回条数 | |
| rank | No | 榜单类型：阅读榜/新书榜/巅峰榜/完结池 | read |
| channel | No | 频道，默认 female | female |
| category | No | 品类关键词过滤（可选），如 '豪门总裁' |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
无 annotations，描述承担了行为披露责任。它明确列出返回字段（书名、作者、在读、状态、章节数、book_id），并主动说明'不含简介全文与版权图'，让代理知道不会得到哪些内容。若补充数据时效性说明会更完整。
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
一句话同时包含动作、筛选维度、返回字段和明确排除项，信息密度高且没有冗余。关键信息前置，结构干净。
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
对于只读榜单查询工具，描述列出的返回字段和排除项配合 100% 参数覆盖的 schema 已足够支撑正确调用。缺少兄弟工具的选择指引，但整体信息完整度良好。
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
输入 schema 对 4 个参数的描述覆盖率为 100%，每个参数的含义、默认值和枚举都有说明。描述文本本身没有额外补充参数格式或边界，因此按规则给予基线 3 分。
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
描述以'读取最新番茄榜单'明确了动作与资源，并列出可选的频道/榜型/品类维度，功能指向清晰。虽然没有明确对比兄弟工具，但'榜单'、'按频道/榜型/品类'的具体范围足以让代理区分于搜索、趋势、热度等兄弟工具。
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
描述通过'最新番茄榜单'暗示了适用场景：需要获取榜单数据时使用。但没有明确说明何时不应使用、或与 fanqie_trend、fanqie_genre_heat 等兄弟工具的取舍，属于可用但未充分引导。
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.