mobi_to_pdf

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

With no annotations, the description carries the full burden of disclosing behavioral traits, but it only mentions 'Requires Calibre'. It does not state whether the operation is read-only, whether the original file is modified, what side effects occur, or what the tool returns. This is a significant gap for a conversion tool.

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 two sentences, front-loaded with the core purpose and followed by a key dependency. No wasted words, every sentence earns its place.

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?

The description covers the basic purpose and a dependency, and the schema documents the two parameters fully. However, with no output schema and no annotations, it omits return value, error handling, and behavioral details, making it only minimally adequate for an agent to invoke reliably.

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 input schema provides descriptions for both parameters, but the file parameter description says 'Absolute path to the PDF file' which is misleading for a mobi-to-pdf converter. The tool description adds no parameter-level clarification and fails to correct this error, so it does not enhance schema semantics.

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 tool converts a Kindle ebook (.mobi) to PDF, using a specific verb and resource. This distinguishes it from sibling tools like epub_to_pdf, txt_to_pdf, and other format converters.

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 implies usage by specifying the input format and output format, making it obvious this is for mobi files among the many conversion siblings. It also notes the Calibre dependency, a prerequisite that helps an agent decide when to use this tool. However, it does not explicitly name alternatives or exclusion cases.

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