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

Annotations cover the mutation/safety profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false), lowering the burden. The description adds that conversion runs via a server-side LibreOffice engine, which hints at fidelity and that OCR is not involved, but it says nothing about whether the call blocks or returns a job handle (job_status is a sibling), nor about output delivery.

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 sentences, front-loaded with the action and scope; the long parenthetical format list is dense but genuinely informative for input validation. The trailing 'use when' sentence is largely redundant 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?

For a conversion tool with no output schema and a sibling job_status, the description should say what comes back (file bytes, URL, job id) and whether processing is synchronous. The input side is well covered, but the return/execution model is left to inference.

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 67%: 'file' (base64, no data: prefix) and 'filename' are documented in the schema, while 'target' is only an enum. The description adds that PDF is the common target and enumerates acceptable input formats, which partially compensates, but gives no detail on the target parameter beyond the enum.

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 (convert) and resource (Office/OpenDocument file) with an explicit supported-input list and the conversion engine. It is clearly distinguishable from pdf_merge/pdf_compress/pdf_ocr by nature, but the description never names a sibling or draws that contrast explicitly.

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?

'Use this when the user needs a document converted' simply restates the purpose and offers no when-not guidance or alternatives (e.g., pdf_ocr for scanned images, pdf_extract_text for text extraction). The only routing hint is the incidental 'most often PDF'.

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