Import a book

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

Without annotations, the description discloses splitting into chapters and size-bounded chunks, and EPUB spine order preservation. It does not mention side effects like overwriting, but the tool name suggests creation. No contradictions.

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 sentences are concise and front-loaded. Every sentence adds meaningful information without redundancy.

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?

The description covers the import process and splitting behavior, sufficient for a tool with no output schema. It is complete given the sibling tools that handle reading and listing.

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%. The description adds value by specifying file extension constraints and the title default behavior for EPUBs, going beyond the schema descriptions.

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 it imports a book from file path or raw text, splits into chapters and chunks, and registers for reading. It clearly distinguishes from siblings like list_books and read_chunk by focusing on the import action.

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 specifies input formats (.txt, .epub, raw text) and EPUB behavior, implying when to use this tool. It lacks explicit when-not-to-use or alternatives but provides sufficient context given the sibling list.

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