add_form_fields_to_pdf

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

Without annotations, the description carries the burden. It discloses that the tool adds interactive fields and saves the resulting PDF to disk, adding useful context. However, it does not explain output file behavior (e.g., whether original is modified), error conditions, or API authentication requirements, leaving significant behavioral ambiguity.

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 efficiently cover purpose, key inputs, and output behavior. No redundant words; front-loaded with the primary action.

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 11 parameters, no annotations, and no output schema, the description provides a solid overview but lacks critical invocation details such as pages spec format, size units, and whether the tool returns anything (e.g., saved file path). It is adequate for initial selection but insufficient for error-free invocation without additional information.

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?

With 0% schema description coverage, the description compensates by naming the core parameters and clarifying that position_x/y are in PDF units and form_field_type restricts to TextBox/CheckBox. However, it leaves 'pages' and 'size' underspecified (format/units) and ignores optional parameters output_dir, output_file_name, and request_doc_name, so coverage is incomplete.

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?

Clearly states the tool adds interactive form fields (TextBox or CheckBox) to a PDF, distinguishing it from sibling tools like add_text_stamp_to_pdf (static text) or fill_pdf_form (filling existing fields). The verb 'Add' and resource 'form field' are specific, and the API endpoint provides additional clarity.

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 usage context through its purpose statement and lists required inputs, but does not explicitly state when to choose this tool over alternatives or provide exclusions. No mention of fill_pdf_form or extract_form_data_from_pdf, leaving the agent to infer the appropriate scenario.

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