convert_pdf_to_word

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the output format ('Output is always DOCX') and references the PDF4me API, but does not disclose potential failure modes, file size limits, or side effects (e.g., whether the input PDF is modified). 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 concise—two sentences—with all essential information front-loaded. It avoids redundancy and effectively summarizes the tool's purpose, required input, optional parameters, and output format without wasting words.

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 tool with 7 parameters and no output schema, the description provides a reasonable overview: it explains the core function, the key options, and the output format. However, it could be more complete by clarifying the exact return value (though 'Output is always DOCX' gives a hint) and any prerequisites or limitations, such as handling of unsupported files or performance implications.

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 71%, which is moderate. The description lists several options (quality, merge_all_sheets, language, OCR, output path) adding slight context beyond the schema, such as the 'Draft/High' values for quality and clarifying 'OCR when needed'. However, it does not explain output_dir and output_file_name in detail, and the schema already covers most parameter meanings, so the added value is limited.

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's function with a specific verb ('Convert') and resource ('PDF file to Word (DOCX)'), making it unambiguous. It also differentiates from sibling tools like convert_pdf_to_excel or convert_pdf_to_powerpoint by explicitly naming the output format.

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 gives clear context for using the tool (local PDF file, provide file path) and implies the use case (converting to Word). However, it does not explicitly mention when to choose this tool over alternatives (e.g., convert_to_pdf, convert_pdf_to_excel) or any exclusions, leaving the guidance implied rather than explicit.

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