parse_pdf_sync

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

No annotations are provided, so the description must fully disclose behaviors. It only mentions synchronous parsing and the API endpoint, omitting key traits such as OCR support, response format, error handling, or resource 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?

The description is a single sentence with no filler, which is concise, but it is too terse to adequately cover the tool's complexity. It sacrifices informative content for brevity.

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 the high parameter count (10) and absence of annotations, the description is severely incomplete. It does not explain return values (despite an output schema existing), parameter usage, or how this tool differs in behavior from its siblings.

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 description coverage is 0%, and the description adds no explanation for any of the 10 parameters. Although names and defaults provide some clues, the description fails to clarify crucial parameters like pdf_path, use_ocr, schema_id, or response_mode, leaving the agent without necessary context.

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's action: parse one PDF synchronously. The verb 'parse' and resource 'PDF' are specific. The term 'synchronously' differentiates from sibling tools like parse_pdf_stream, submit_parse_job, and submit_parse_batch, making its purpose distinct.

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?

No explicit guidance on when to use this tool versus alternatives. Only the word 'synchronously' suggests immediate result, but there is no reasoning about when to prefer synchronous parsing over streaming or batch modes.

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