convert_book_to_word

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

No annotations exist, so the description carries the full behavioral burden. It does disclose the produced artifacts and a key quality trait (strict RTL Arabic layout fidelity), but is silent on overwrite behavior, whether output_dir is optional/defaulted, runtime, and failure modes for missing or unsupported files.

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?

A single front-loaded sentence with no filler; the action, input, outputs, and differentiator all appear immediately. Nothing is wasted or buried.

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 low-complexity, two-parameter tool with a fully documented schema and no output schema, the description covers the essentials. However, with zero annotations it should still state overwrite/creation semantics and the default behavior when output_dir is omitted, which it does not.

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 100%, so both parameters are already documented in the schema, making 3 the baseline. The description adds no meaning beyond it — it never mentions file_path, output_dir, defaults, or accepted input formats despite saying 'PDF or document' while the schema says 'input PDF book'.

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 a specific verb+resource pair ('Converts a single PDF or document') and names both output artifacts (.docx and .md), which is far more informative than the name alone. The word 'single' implicitly separates it from batch_convert_folder, but no sibling is named explicitly, so an agent must infer the distinction.

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?

Usage is only implied: 'single' hints that one file at a time is handled, suggesting batch_convert_folder for folders, but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent can guess the routing but is not told it.

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