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

No annotations are present, so the description carries the transparency burden. It does disclose that the read is one-shot and warns that long works are heavy, but it does not explain truncation, response format, or performance implications beyond that.

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 sentences with no filler, front-loading the core action and then adding a relevant caution. Every sentence earns its place.

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 simple two-parameter read tool, the description plus schema is usable, and the search_novels suggestion is helpful context. However, with no output schema and no annotations, the return behavior and truncation semantics remain somewhat implicit.

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?

The schema already documents max_chars with its truncation cap and default. The description adds only context that novel_id refers to an entire work, not a chapter; it provides little meaning beyond the schema for a parameter that is otherwise undocumented.

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 action: 一次性读取整部作品的全部正文, so the agent knows this tool returns the complete full text of a work rather than metadata or a single chapter. It implicitly distinguishes itself from read_chapter and related tools, though it does not explicitly name them.

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?

The description gives concrete routing advice: for long works, prefer search_novels first to pinpoint content. It does not mention when to use this over read_chapter, but the caution about large content and the explicit alternative tool provide useful selection context.

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