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 does: it discloses latency ('30 seconds or more'), the privacy model (uploaded to the Papyrio API, processed in memory, not stored), destructive behavior (output_path is replaced if it exists), the return value (path and size in bytes), a 50 MB input cap, and per-call quota consumption.

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?

Single dense block, front-loaded with the verb and supported formats, with constraints following. Nearly every clause carries actionable information, though the privacy and quota details could be split more cleanly for scanning.

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 two-parameter conversion tool with no output schema, everything an agent needs is present: accepted formats, output destination behavior, size limit, failure mode (encrypted files), runtime expectations, and the shape of the return value.

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 already 100%, so the baseline is 3; the description adds meaning beyond it by explaining that output_path is overwritten and that the resolved path is returned, and by noting the extension drives parsing. It does not restate the default suffix logic, but that is fully covered in 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?

States a specific verb and resource ('Convert a Word (.doc, .docx, .odt), PowerPoint ... or Excel ... document to PDF') with all supported extensions and the engine used. It is clearly distinguishable from siblings such as pdf_to_word (reverse direction) and image_to_pdf/webpage_to_pdf (different sources).

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?

Explicitly gives the use case ('turn an Office file into a fixed, shareable PDF') and an exclusion ('not for files that are already PDFs'), plus a hard constraint that password-protected Office files are not supported. No alternatives need inferring.

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