add_books

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does reveal two useful traits: books with matching title+author are skipped and reported as 'duplicate', and the Calibre GUI must not hold the library open. However, it does not mention whether files are copied or moved, whether directory traversal is recursive, what happens on partial failure, or any other side effects, leaving notable behavioral gaps.

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 well-structured: a one-line purpose statement, two concise behavioral caveats, and an Args section with a single parameter definition. No sentence is wasted, and the most important usage constraints are front-loaded before the parameter details.

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 single-parameter import tool with an output schema present, the description covers the essential prerequisites: absolute path semantics, file-or-directory inputs, duplicate handling, and the GUI-lock constraint. It does not mention whether folders are processed recursively or which ebook formats are supported, but these are minor gaps given the tool's simplicity and the availability of an output 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?

The input schema only defines 'paths' as an array of strings with no description (0% schema coverage). The description fully compensates by specifying that paths must be 'Absolute paths' and can point to 'ebook files or folders containing ebooks.' This directly adds crucial meaning that the schema lacks, making the parameter semantics clear and unambiguous.

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 verb, 'Import', and a clear resource, 'ebook files (or directories of ebooks) into the library.' It clearly differentiates from most siblings like search_books, list_books, and read_book. However, it does not explicitly distinguish itself from the sibling 'import_inbox', which may represent an overlapping alternative, so the differentiation is not complete.

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 provides clear operational context, explicitly stating that the Calibre GUI must not hold the library open while adding. It also explains the duplicate-skipping behavior, which helps an agent anticipate outcomes. However, it does not mention any alternative tools or conditions under which a sibling like import_inbox would be more appropriate, so exclusions are absent.

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