novel_outline

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

No annotations are provided, so the description carries the full disclosure burden. It says materials are 'initialized, read, updated' but never states whether writes overwrite existing files, are idempotent, destructive, or require an existing directory — meaningful given this tool obviously mutates files on disk.

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?

A single dense sentence front-loads the resource scope and then enumerates the artifacts, with no filler. It is efficient, though the enumeration is long and slightly list-like rather than prioritized.

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 an 11-parameter, 7-action tool with no annotations and no output schema, the description covers the scope of managed artifacts but not how the actions relate, what persists, or what a read returns. Adequate as a minimum but leaving gaps an agent would have to resolve from the schema alone.

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 description coverage is 100%, so every parameter including the action and file enums is already documented inline. The description reinforces the file categories but adds no format, default, or interaction detail beyond the schema. Baseline 3 applies.

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 gives a specific verb set (初始化、读取、更新) plus a concrete resource: the creative-material files under novels/创作资料/<书名>/. It enumerates the artifact types (创作设定/主要人物/次要人物/剧情大纲/钩子记录/创作状态卡), which maps well onto the file variants. It does not differentiate itself from the many siblings that also touch novel data, so it falls short of a 5.

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?

There is no statement of when to choose this tool over novel_read, novel_books, novel_chapters, novel_plot or novel_settings, all of which plausibly overlap. No prerequisites, no exclusions, no ordering guidance. Usage must be inferred entirely from the action enum in the schema.

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