office_export_pdf

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

Annotations already declare the mutation/destruction profile (destructiveHint=true, idempotentHint=false), so the description earns credit for adding non-structured context: output is a separate file, no visible window, hidden Office on Windows, and a LibreOffice fallback. It still does not explain overwrite semantics, which is the operation's main destructive behavior.

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, front-loaded with the conversion and engine mechanism, followed by the non-obvious side effects (separate file, no visible window). No filler.

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?

Annotations cover the safety profile and no output schema is needed, but the definition omits overwrite/outputPath semantics and any disambiguation from office_convert_to_pdf. Adequate but with clear, actionable gaps for a 4-param converting tool.

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 50%: path and outputPath are documented in-schema, but engine and overwrite are not. The description's mention of a 'LibreOffice fallback' implies the engine choice, but the destructive overwrite parameter is left entirely undocumented in both places, so it only partially compensates.

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 gives a specific verb (export) and resource (XLSX/DOCX/PPTX to PDF) with the added qualifier 'reviewable'. However, it never distinguishes itself from the sibling office_convert_to_pdf, which appears to overlap directly, so an agent cannot route between the two from this text alone.

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 hints at engine context ('hidden native Microsoft Office on Windows, with optional LibreOffice fallback'), which implies when each engine applies, but it never states when to use this tool versus office_convert_to_pdf or any prerequisite/exclusion. Usage is only implied.

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