word_to_pdf

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

With no annotations present, the description carries the burden of behavioral disclosure. It adds a useful dependency note (Requires LibreOffice) but does not describe the conversion process, output filename behavior, error handling, or whether the original file is modified. This is minimal for a tool that could have side effects.

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 concise sentence that delivers the core purpose and a key dependency. No filler or redundancy.

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 essential purpose and dependency, and the schema provides the remaining parameter details. However, it omits details like output behavior (unless inferred from the output_name parameter) and potential error conditions (e.g., missing LibreOffice). Given its simplicity, it is average but not fully complete.

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 has descriptions for both parameters, though the 'file' parameter description incorrectly says 'Absolute path to the PDF file' instead of the Word document. The tool description does not add any additional parameter meaning beyond the schema. The baseline of 3 applies due to high schema coverage, though the schema error could mislead an agent.

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 specific conversion action (Word to PDF), includes the supported formats (.doc/.docx), and mentions a key dependency (LibreOffice). This distinguishes it from sibling conversion tools like markdown_to_pdf or pdf_to_tiff.

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 implicitly provides usage context: it is for converting Word documents to PDF. It does not explicitly exclude other formats or name alternative tools, but the scope is clear. It also notes the LibreOffice requirement as a prerequisite.

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