import_inbox

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

With no annotations provided, the description fully carries the behavioral burden and does so well. It discloses the environment variable requirement and the exact file disposition side effects: successful files and duplicates move to `<inbox>/imported/YYYY-MM/`, while failed files move to `<inbox>/failed/` for inspection. This is strong transparency for a tool that mutates the filesystem.

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 primary purpose, followed by prerequisites and side effects. Every sentence earns its place, with no filler or repetition of schema content.

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 zero-parameter tool with an output schema present, the description is complete: it states what is imported, what configuration is required, and what happens to files in each outcome case. An agent has enough information to invoke the tool correctly and predict its effects.

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?

There are no input parameters, so the schema requires no explanation. The description still adds relevant operational context by referencing the CALIBRE_INBOX_DIR environment variable, which effectively serves as the tool's input. Baseline 4 is appropriate for a zero-parameter tool.

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 names a specific verb and resource: 'Import every ebook file in the configured inbox folder into the library.' It clearly distinguishes this from siblings like add_books by emphasizing batch import from a configured inbox folder rather than individual file addition.

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 context is clear: this tool processes all ebook files in the inbox folder, and the CALIBRE_INBOX_DIR prerequisite is stated. However, it does not explicitly name alternatives or state when not to use it relative to add_books or other sibling tools, so it stops just short of full routing guidance.

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