office_to_pdf

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

With no annotations, the description carries the full burden, and it does disclose genuinely useful traits: server-side LibreOffice execution ('no Office installation needed anywhere') and a per-page cost of $0.01, which matters for planning. It says nothing about output behavior (where the PDF lands, whether output_path is created/overwritten) or auth, so gaps remain.

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?

It is a single dense sentence plus a short pricing clause, front-loaded with the core verb and format list. The parenthetical format enumeration is long but earns its place; nothing is wasted.

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?

For a tool with no annotations, no output schema, and 0% parameter documentation, the description should say more about outputs and the two undocumented parameters. It adequately covers the input document and cost but leaves the return value and output_path/idempotency_key semantics unexplained.

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 0% on three parameters, so the description must compensate. It clarifies that 'file' is a local path and implicitly which formats are valid, but 'output_path' and 'idempotency_key' receive no explanation at all, leaving two of three parameters undocumented.

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+resource ('Convert an Office document ... to PDF') and enumerates all accepted input formats, so the agent knows exactly what the tool consumes and produces. It also names the underlying mechanism (server-side LibreOffice), which disambiguates it from generic renderers like 'render'.

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?

Usage is only implied by the format list and the phrase 'local path' — there is no explicit when-to-use statement, no when-not, and no routing to alternatives such as 'render' or 'md_to_docx'. The agent must infer the boundary itself.

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