pdf_fill_form

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

Annotations indicate idempotentHint=true and destructiveHint=false, so the description's mention of filling fields aligns. It adds that flatten can make fields non-editable and notes font requirements for non-Latin text. However, it does not disclose behavior like overwriting existing field values or error handling. No contradiction with annotations.

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 purpose, followed by key details (supported field types and font requirement). Every sentence is essential; no fluff.

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 5 parameters, complete schema coverage, and no output schema, the description adequately covers key aspects: supported field types, required font for non-Latin text, and flatten effect (via parameter). Missing: output path requirements or error scenarios, but schema covers the former.

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 baseline 3. The description adds that field values can be strings or booleans (matching schema) and mentions list-box multi-select fields (not fully captured in schema type constraints). Does not explain parameters like outputPath or flatten beyond what schema provides.

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 ('Fill form fields in a PDF') and specifies supported field types (text, checkbox, dropdown, radio, list-box). It distinguishes itself from sibling tools like pdf_get_form_fields (which reads fields) and pdf_flatten (which only flattens without filling).

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. It implies usage for filling forms but does not mention prerequisites (e.g., the PDF must have form fields) or when not to use it (e.g., for flattening alone, use pdf_flatten). No comparison to sibling tools.

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