pptx_export_pdf

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

With no annotations provided, the description fully carries the burden of behavioral disclosure. It details concurrency via unique -env:UserInstallation, all possible error types (ERR_FILE_NOT_FOUND, ERR_UNSUPPORTED_FMT, etc.), and the return format. No contradictions.

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 and front-loaded with the main purpose, but it is somewhat lengthy (includes Args, Returns, Raises sections). Every sentence adds value, though a slightly more concise version would be possible.

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's complexity (3 parameters, no output schema but return format described), the description covers prerequisites, output creation, and all error scenarios. It is complete for an agent to use the tool effectively.

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 0% description coverage, but the description fully compensates by detailing each parameter: path ('Path to an existing .pptx'), output ('Target path...parent directory created if not exist'), and folder ('Optional base folder for relative paths'). This adds significant 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 .pptx file to PDF via LibreOffice headless,' which is a specific verb-resource pair. It distinguishes itself from sibling export tools like pptx_export_html by focusing on PDF output.

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 usage for PDF conversion but does not provide explicit alternatives or when-not-to-use scenarios. The purpose is clear, but no direct guidance on when to choose this over other export tools.

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