list_novels_tomatoFetch real novel IDs from the Fanqie Novel author backend to verify and backfill records. Sync to a local registry for batch uploads when needed.
读取作者后台真实小说列表（拿真实 book_id），用于核对与回填。可选把结果同步进本地小说登记（供批量上传用）。
| Name | Required | Description | Default |
|---|---|---|---|
| sync_local | No | 是否把后台书籍同步为本地小说登记（默认 false） |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses that the tool reads the remote backend and can optionally sync results into a local registry, but it omits authentication requirements, sync overwrite/merge behavior, and error conditions.
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?
The description is two compact sentences with no filler. It front-loads the core read action and follows with the optional sync side effect.
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?
For a one-parameter tool with no output schema, the description supplies the main return concept, real book_id, and the optional side effect. It could be more complete by stating the login/cookie prerequisite, but the essential call context is present.
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 coverage is 100%, so the boolean parameter is already documented. The description adds useful intent beyond the schema by explaining that syncing is for batch upload, though it does not add format or edge-case semantics.
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?
The description states a specific verb and resource: reading the author backend's real novel list. It also clarifies the key output, real book_id, and distinguishes this from a local registry, so an agent can tell what the tool returns.
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?
It gives clear usage context: verifying/backfilling and optionally syncing for batch upload. It does not explicitly name when not to use it or point to an alternative sibling, so it stops short of full routing guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.