fill_pdf

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

The description discloses key behaviors: how AcroForm fields are filled natively vs. drawn for others, and that warnings flag values that are shrunk/truncated. Since no annotations exist, the description carries full weight. However, it lacks details on failure modes or access requirements.

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 very concise: three sentences without any redundant text. The first sentence states the core purpose, followed by terse but necessary details. Every sentence adds value.

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 output schema exists (not shown), the description need not detail return values. It covers the main filling behavior and the warning list. Still, it omits edge cases like invalid field IDs or missing output paths, but these are minor for a tool of this complexity.

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?

The explanation of `values` (field id->text mapping, checkbox handling) adds meaning beyond the schema, and `output_path` is implied. However, `flatten` is not mentioned at all, and schema coverage is 0%, so the description does not fully compensate for the missing parameter documentation.

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 fills a PDF and saves it, which is a specific verb+resource. While it does not explicitly distinguish from sibling tools like render_filled_preview, the 'save it' part differentiates it from pure rendering tools. Overall, the purpose is unambiguous.

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 no guidance on when to use this tool versus alternatives. It does not mention prerequisites, when not to use it, or which sibling tools are better suited for specific scenarios. The only usage hint is implicit from the description's focused task.

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