djvu_to_pdf

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 mentions the DjVuLibre dependency but does not describe output behavior, potential overwriting, error conditions, or any side effects. This is insufficient for a tool that creates a new file.

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, front-loaded sentence providing the core purpose and a critical prerequisite. Every word earns its place; there is no fluff or unnecessary detail.

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 straightforward conversion tool with no output schema, the description covers the basic purpose and dependency, but lacks context about the output file path behavior (e.g., defaults, overwriting) and does not address the incorrect schema description. It is minimally complete but has clear gaps.

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% so the baseline is 3, but the parameter descriptions are misleading: 'file' is described as 'Absolute path to the PDF file' while the tool converts DjVu to PDF. The tool description does not add any clarifying parameter semantics, missing the opportunity to correct this inconsistency.

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 'Convert a DjVu document to PDF' with a specific verb and resource, unambiguously identifying the tool's function and distinguishing it from sibling converters like pdf_to_tiff or epub_to_pdf.

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 implicitly establishes when to use this tool (when a DjVu file needs conversion) by being one of many format-specific converters. It adds the prerequisite 'Requires DjVuLibre,' which is important context, but does not explicitly mention alternatives or exclusions.

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