epub_to_pdf

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

No annotations are present, so the description carries the burden. It discloses a key behavior: 'extracts text content', which alerts users that images or rich layout may be lost. However, it does not cover side effects, output behavior, or any permissions or failure conditions, leaving transparency incomplete.

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 with no redundant words. Every part—conversion action, source/target formats, and the text-extraction caveat—earns its place, making it maximally concise.

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 2-parameter conversion tool with no output schema or annotations, the description covers the core purpose and a limitation. However, it does not mention return values, output path behavior (though schema does), or potential pitfalls like DRM or image handling. It is adequate but could be richer in context.

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%, but the description for 'file' incorrectly says 'Absolute path to the PDF file' while this tool actually converts EPUB to PDF. The tool description clarifies that 'file' refers to the EPUB input, thus adding corrective meaning beyond the schema. Output_name is adequately described.

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 uses the specific verb 'Convert' and clearly states the resource: 'EPUB ebook to a PDF'. It also adds a differentiator by noting 'extracts text content', which distinguishes it from other conversion tools like markdown_to_pdf or cbz_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 intended use is implied by the conversion context: when you need to convert an EPUB file to PDF. However, no explicit when-to-use vs alternatives, exclusions, or 'use X instead' guidance is provided. The mention of text extraction hints at limitations but does not name direct alternatives.

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