pdf_to_json

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

No annotations are provided, so the description must carry the full behavioral burden. It reveals the output contents (preserved text, fonts, images, vectors) and the underlying endpoint, but does not disclose whether the call is asynchronous, whether an API key is strictly required, any side effects, or what happens with failures. This leaves critical behavioral gaps for an agent.

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 main action, and includes a reference link for additional detail. No filler or redundant content—every part contributes to understanding the tool's purpose.

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 converter with 11 parameters and no output schema, the description is incomplete. It does not explain the return format or whether the tool returns the JSON directly or a job ID to poll via wait_job_completion, which is essential for correct invocation in this toolset. The high schema coverage helps but cannot compensate for the missing async/return behavior.

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?

The schema covers all parameters with descriptions, meeting the >80% threshold, so the baseline is 3. The description adds no parameter-specific meaning beyond the schema; it neither clarifies parameter interactions nor highlights the most important inputs like url or lang.

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 action (Convert PDF and scanned images) and the resource/output format (JSON representation with text, fonts, images, vectors, and formatting preserved). It distinguishes from sibling converters like pdf_to_text or pdf_to_csv by specifying the JSON output and preserved elements.

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 context is implied through the purpose: use when a JSON representation with full formatting (text, fonts, images, vectors) is needed. However, there are no explicit exclusions or comparisons to sibling tools like pdf_to_text or pdf_to_csv, so an agent must infer when this tool is the right choice.

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