pdf_to_word

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 the upload destination (Papyrio API), that processing is in-memory and non-persistent, that output_path is overwritten destructively, the 50 MB input cap, and that each call consumes one unit of daily quota. These are exactly the operational facts an agent cannot infer elsewhere.

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?

Front-loaded with purpose and the scanned-PDF caveat before operational details, and nearly every sentence adds distinct information. It is dense but not padded; one could argue the privacy sentence and quota sentence are separable, but both are load-bearing for agent behavior.

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 no annotations and no output schema, the description covers safety (overwrite), limits (50 MB, quota), data handling, failure-mode routing (scanned PDFs), and return shape. An agent has everything needed to call it correctly and to know when to call ocr_pdf instead.

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 the baseline is 3, but the description adds value the schema does not: it explains that the result is written to output_path and that any existing file there is replaced, clarifying the destructive side effect of that parameter. It also states the call returns the path and byte size, which compensates for the absence of an output 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 PDF into an editable Word document') and immediately distinguishes itself from pdf_to_jpg, extract_pdf_text, and office_to_pdf by naming the output format. The routing sentence about scanned PDFs further separates its domain from ocr_pdf.

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?

Gives explicit when-it-works conditions (Word, Google Docs, InDesign exports) and an explicit when-not plus alternative ('A scanned PDF is a picture of a page, so run ocr_pdf on it first'). This is exactly the agent routing signal that matters when ten sibling conversion tools exist.

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