PDF to EPUB

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

Annotations declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, so the write/safety profile is already covered. The description usefully narrows the scope to 'a PDF's text', implying images and layout are not carried over, but it omits that the output path must not already exist and says nothing about failure modes or metadata handling.

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?

One tightly written sentence that front-loads the conversion and appends the splitting nuance. No filler, no restatement of the tool name.

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?

An output schema exists so return values need not be explained. For a 6-parameter converter the description is adequate but leaves gaps: it never warns that a text-only extraction loses images/layout, nor that the target file must not exist, both of which affect correct invocation.

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 50%, and the description only elaborates the 'split' behavior ('chapters at headings (or every few pages)'), which is genuinely helpful for interpreting the headings/pages enum. The title, author, and language parameters get no added meaning in either the description or 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?

States a specific verb and resource conversion ('Convert a PDF's text into an EPUB 3 e-book') and adds the chapter-splitting behavior. The destination format inherently separates it from pdf_to_docx and pdf_to_pptx, though it never names an alternative or scoping condition, so it lands just shy of a 5.

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?

There is no when-to-use, when-not-to-use, or alternative routing guidance; the agent must infer that this is the EPUB path versus pdf_to_docx/pdf_to_pptx. The parenthetical about splitting at headings or every few pages describes behavior, not when to pick this tool over a sibling.

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