批量上传章节

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden and does substantial work: it discloses sequential ordering, rate limiting, failure isolation (单章失败不中断), per-chapter results, and the draft-avoidance rationale for confirm=false. It omits auth prerequisites and the irreversibility/side effects of a real publish, which login_qimao-style context only implies.

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?

Two clauses, front-loaded with the core action, then the failure/return behavior, then the confirm caveat. Dense but every clause carries information; minor density from stacked modifiers keeps it just under 5.

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 7-parameter mutation tool with no annotations and no output schema, the description covers ordering, rate limiting, failure semantics and the dry-run mode well. Remaining gaps are the result format (返回逐章结果 is named but not defined) and the book_id/novel_id resolution, though the latter is documented in the 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 coverage is 100% (baseline 3), and the description adds meaningful semantics beyond the schema text: confirm=false does not merely skip publishing, it dry-runs only the first chapter to avoid accumulating drafts, and rate limiting is tied to the interval between chapters.

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?

States a specific verb (上传/发布) and resource (待发布章节 from 本地文稿库), plus scope details: selects chapters in chapter-number order, rate-limited, sequential. It clearly distinguishes itself from the single-chapter sibling add_chapter_qimao by being the batch path.

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?

Gives explicit context: use it to pick 「待发布」 chapters from the local library, and use confirm=false to dry-run only chapter 1 without leaving drafts in the backend. It does not explicitly name add_chapter_qimao as the alternative for single uploads, so it stops short of full when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.