Novel

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

The action list implies effects such as create, end, archive, and checkpoint_remove, and the annotations indicate read-write open-world behavior. However, the description does not elaborate on side effects, persistence, or how open-world changes propagate beyond the save file.

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 compact and front-loaded with the action list, followed by clear use and non-use guidance. There is no redundant prose or unnecessary detail.

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 tool with many actions and parameters, the description gives a useful high-level frame but leaves operational details—such as action-specific behaviors, return data, and how context saving/checkpointing works—to be inferred from the schema or elsewhere.

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%, and each parameter description includes the action(s) it applies to. However, most descriptions are terse labels (e.g., 'Genre tag (create/genre)') and enum values are repeated from the schema without deeper explanation, so semantic depth is limited.

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 clearly identifies the tool as managing Novel save files for campaign lifecycle, interchange, and return points, and explicitly contrasts it with entity-content tools. It lists the main action categories, though a few subactions like checkpoint_set are only implied by the umbrella term 'checkpoint'.

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?

Explicit 'Use when' and 'Do NOT use when' guidance is provided, with a clear pointer to entity tools for content management. This makes it easy for an agent to decide when to invoke this tool versus its siblings.

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