pdf_to_docx

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

With no annotations, the description carries the transparency burden. It discloses the critical requirement 'Requires LibreOffice', which is useful. However, it does not mention any potential side effects, limitations (e.g., formatting fidelity), or whether the original PDF is modified, leaving gaps in behavioral transparency.

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 concise, front-loaded sentences. Every word adds value: the first defines the conversion, the second gives a crucial dependency. No fluff 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?

For a simple conversion tool with two well-schema-documented parameters, the description is nearly complete. It covers the main purpose and the key prerequisite. It lacks explicit guidance on output defaults or usage scenarios, but these are either in the schema or inferable, so only a minor gap remains.

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 already documents both parameters with full coverage (100%), so the description adds no new parameter information. The schema descriptions are sufficient, and the tool description's mention of 'convert' implies the role of the file parameter but does not enhance the semantics beyond 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?

The description states 'Convert a PDF to a Word document (.docx)' with a clear verb and resource, and the output format is explicitly named. This distinguishes it from sibling conversion tools like pdf_to_markdown 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 gives a clear context (converting PDF to Word) but does not explicitly state when to use this tool over alternatives or mention any exclusions. It does note a prerequisite (LibreOffice), which hints at usage requirements, but no explicit alternative guidance.

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