Convert an Office file to PDF

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

Annotations already declare the safety profile (readOnly=false, destructive=false, idempotent=true), so the bar is lower, and the description adds real value on top: the LibreOffice dependency and the specific failure mode ('fails with an install hint'). It does not add rate-limit or overwrite behavior beyond what the schema already states.

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?

Two tight sentences: the conversion and supported formats are front-loaded, and the dependency/failure caveat follows. 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?

With an output schema present and annotations covering the safety profile, the description only needs to cover formats and the external dependency, both of which it does. An agent has everything required to invoke it 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?

Schema coverage is 100%, so both parameters (input, output) are fully documented in the schema, including the allowed-folder and no-overwrite constraints. The description's format list loosely maps to the input parameter but adds no syntax or path-format detail beyond the schema, so baseline 3 applies.

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 a precise verb+resource ('Convert ... to a new PDF') and enumerates the exact accepted source formats (.docx, .xlsx, .pptx, .odt, .ods, .odp). This distinguishes it cleanly from the other source-specific conversion siblings like pdf_from_images and pdf_from_markdown without needing to open any schema.

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?

It clearly establishes the context of use (an Office/OpenDocument file on this computer) and the prerequisite (LibreOffice installed), which routes the agent appropriately. It stops short of naming an alternative tool or stating when-not to use it, so it is clear context without explicit exclusions.

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