excel_export_pdf

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

With no annotations, the description fully discloses behavior: it uses LibreOffice headless, employs a unique per-call user installation for concurrency, creates parent directories for output, and raises specific errors. This exceeds typical 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 well-structured with summary, Args, Returns, and Raises sections. Every sentence is informative and necessary, with no wasted words. It is both concise and comprehensive.

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 complexity of the tool and the rich sibling context, the description covers purpose, parameters, return format, concurrency behavior, and error conditions. It is fully sufficient for an agent to select and invoke the tool correctly.

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?

Despite 0% schema description coverage, the description thoroughly explains each parameter: path is an existing .xlsx, output is target path with directory creation and relative resolution against folder, and folder is an optional base. This adds critical meaning 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 explicitly states 'Convert a .xlsx file to PDF via LibreOffice headless,' providing a specific verb and resource. It clearly distinguishes this tool from other export tools like excel_export_csv and convert_document.

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 implies when to use this tool (for .xlsx to PDF conversion) and notes prerequisites (LibreOffice on PATH), but it does not explicitly exclude other tools or provide alternative recommendations. The Raises section lists error conditions that help guide usage.

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