parse_pdf_form_fields

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

With no annotations, the description carries the behavioral burden. It does disclose the output type (structured JSON), the specific data extracted, and the payment cost, making it more than a tautology. However, it omits input format expectations, error behavior for non-fillable PDFs, and limitations around XFA vs AcroForm.

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?

A single dense sentence front-loads the core function, extraction targets, and output format, followed by a concise pricing note. Every clause earns its place.

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?

There is no output schema and no concrete guidance on what the 'payload' string should contain (e.g., base64-encoded PDF, file URL, or path). An agent cannot confidently construct a valid invocation for this tool from the description alone, which is a critical gap for a document-parsing tool.

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 schema already documents the two parameters. The description does not add meaning about how to provide the PDF inside the generic 'payload' string, but it does not need to re-explain parameters given the full schema coverage.

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 ('parses') and resource ('fillable PDF documents'), and lists concrete extraction targets: AcroForm dictionary keys, checkboxes, and signature metadata. This distinguishes it from PDF siblings like pdf_page_rasterizer_highres or pdf_table_stream_extractor_resilient.

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 for extracting form-field data from fillable PDFs, which gives an agent reasonable context. However, it does not explicitly state when not to use it or name alternatives such as pdf_form_xfa_acroform_flattener for XFA handling.

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