batch_convert_folder

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

With no annotations, the description carries the behavioral burden and does disclose meaningful traits: sequential processing, low memory use, automatic timestamped ZIP bundling, and resume state. It still omits important mutation and safety behavior, including overwrite behavior, permissions, error handling, and how resume state is used.

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 definition is two front-loaded sentences with little waste, and the key batch scope appears immediately. The example parenthetical is helpful, though the second sentence could be slightly more tightly tied to the parameters.

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?

This is a complex batch mutation tool with no annotations and no output schema, so the description needs to explain more than a simple read tool. It covers core batch behavior but leaves out return/progress behavior, error handling, and safety details an agent would need before invoking it confidently.

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 description coverage is 100%, so the schema already explains all three parameters. The description reinforces the bundle count concept via 'every N books' and mentions output ZIP bundles, but it adds no syntax, constraints, or edge-case semantics beyond the schema.

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 gives a specific verb and resource (batch conversion on an entire folder) and clarifies scope with examples like 150+ books. It separates itself from single-book conversion implicitly, though it does not name sibling tools such as convert_book_to_word or get_batch_status.

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 phrase 'entire folder' and the large-book example imply when to use this over a single-book conversion. However, there is no explicit when-not guidance, no mention of prerequisites, and no named alternatives such as get_batch_status for checking progress.

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