batch_convert_to_epub

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, but it only restates the action without revealing side effects, error behaviors, or dependencies. It doesn't mention whether it overwrites files, requires a prior setup, or what happens if volume_ids is null. This is essentially a tautology of the tool's name with no additional behavioral context.

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 a single, concise sentence that gets straight to the point. It is front-loaded with the action and has no unnecessary filler. However, it could be considered too minimal, as it omits useful details, but for conciseness alone it is efficient and well-structured.

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 batch operation with two parameters and existing sibling tools like set_library_path and convert_volume_to_epub_file, the description is incomplete. It doesn't explain the relationship to these siblings, any required setup, or what happens when volume_ids is omitted. Even with an output schema, the agent lacks critical context about prerequisites and behavior.

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 description coverage is 100%, so the parameters are fully documented in the input schema. The description adds no additional meaning about the parameters, such as how volume_ids interacts with output_dir or any constraints. Since the schema already covers the semantics, the baseline of 3 is appropriate.

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 clearly states the action (convert), the resource (multiple Directmedia volumes), and the output format (EPUB). It implicitly distinguishes from the sibling convert_volume_to_epub_file by the word 'multiple', but it doesn't explicitly name the alternative. This is a clear and specific purpose, though not perfect at differentiating siblings.

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 no guidance on when to use this tool versus the single-volume conversion tool or any other alternative. It doesn't mention prerequisites like setting the library path, nor does it specify conditions for batch vs. single conversion. There is no exclusion or alternative mention, leaving the agent to infer usage.

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