translate_pdf

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

With no annotations provided, the description carries the full burden. It discloses preservation of mathematical formulas and layout, plus the return structure (dual and mono versions). However, it does not mention prerequisites like needing a warmed-up translator, potential file overwrites, or other side effects, leaving significant behavioral gaps.

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?

The description is concise and well-structured, starting with the main purpose, followed by Args and Returns sections. It is front-loaded with the core action. Some redundancy exists because the Args section repeats schema descriptions, but overall it is efficient and easy to parse.

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?

The tool is simple with two parameters and an output schema exists (as indicated by context signals), so the description does not need to explain return values in detail. It covers the core behavior and output. However, it omits mention of the warm_up_translator sibling as a prerequisite, which is a minor completeness gap.

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% because both pdf_path and output_path have descriptions that match the Args section. The description adds no new meaning beyond the schema; it merely restates the parameter definitions. Baseline 3 is appropriate since the schema fully documents the parameters.

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 clearly states the tool translates a PDF document via PDFMathTranslate-next, with preservation of formulas and layout. This specific verb+resource combination distinguishes it from sibling tools like pdf_get, warm_up_translator, and check_translation_tool.

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?

The description implies the tool is used for translating PDFs, but does not explicitly state when to use it versus the sibling tools (e.g., whether warm_up_translator should be called first). There is no direct alternative or exclusion guidance, only an implied purpose.

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