pdf_fill_form

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

Annotations already declare idempotentHint=true and destructiveHint=false, establishing the safety profile. The description adds valuable capability context by enumerating supported field types (text, checkbox, dropdown, radio) and specific font use cases (Arabic, CJK), though it omits error behavior or edge case handling.

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?

Three sentences with zero waste: the first establishes the action, the second details supported field types, and the third provides critical font guidance. Information is front-loaded and 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?

Given the rich input schema (100% coverage) and comprehensive annotations, the description adequately covers the tool's purpose. However, it misses the opportunity to describe the typical workflow with pdf_get_form_fields sibling tool, which is essential for practical usage.

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 100% schema description coverage, the baseline is 3. The description minimally adds value by mentioning specific field types and giving font examples (Arabic, CJK) not explicitly listed in the schema, but largely repeats information already present in the structured parameter descriptions.

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 core action ('Fill form fields') and resource ('in a PDF'), distinguishing it from sibling tools like pdf_add_watermark or pdf_merge. However, it does not explicitly clarify whether it modifies in-place or creates a new file (though outputPath implies this).

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 provides implicit guidance by listing supported field types and noting the fontPath requirement for non-Latin text. However, it lacks explicit 'when to use' guidance, such as mentioning the prerequisite use of pdf_get_form_fields to retrieve field names before filling.

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