word_export_pdf

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

With no annotations, the description fully bears the burden. It discloses concurrency via unique UserInstallation per call, error types (ERR_FILE_NOT_FOUND, etc.), and behavioral details like parent directory creation and relative path resolution.

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 long but well-structured with Args, Returns, Raises sections. It is informative without being overly verbose, though some detail on concurrency could be shortened.

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?

Given the tool complexity (3 parameters, error handling, concurrency) and the presence of an output schema, the description covers inputs, output format, errors, and behavioral context completely.

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 0%, but the description adds detailed meaning for each parameter: path (existing .docx), output (target PDF, parent dir created, relative resolved), folder (optional base for relative paths). This significantly adds beyond the 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 clearly states it converts .docx files to PDF using LibreOffice headless, with specific verb 'Convert' and resource '.docx file to PDF'. It distinguishes from siblings like word_export_html and excel_export_pdf by focusing on Word-to-PDF conversion.

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 explains what the tool does but does not explicitly indicate when to use it over alternatives like word_export_html or convert_document. It mentions concurrency but lacks guidance on when not to use or when to choose siblings.

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