camelot_pdf_filler

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

Annotations include readOnlyHint=false and destructiveHint=false, but the description's phrase 'export a clean vector PDF with zero watermarks' is promotional rather than behavioral. It does not disclose key traits like whether the original file is modified, auth requirements, or processing limits, which is a gap given the annotations do not cover these.

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 compact and front-loaded with the core functionality, but includes promotional phrases ('100% free with no limits..') and a canonical URL that do not aid tool selection. It could be more concise by removing marketing 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?

For a tool with two parameters and no required fields, the description covers the basic use case. However, it omits details on how to specify the PDF file upload (no file parameter in schema), which is a significant gap. The output schema exists, so return format is not needed, but the input method is unclear.

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 description coverage is 100%, providing clear descriptions for both parameters. However, the description adds no explanation of how to construct the sampleFieldMapping JSON structure, which is critical for correct usage. It adds value in explaining the purpose of the formTitle but leaves the mapping object undocumented beyond the schema.

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's purpose: uploading a PDF, filling form fields, adding text and signatures, and exporting a clean vector PDF. It distinguishes itself from siblings like camelot_pdf_merger by focusing on filling rather than merging, though it doesn't explicitly name alternatives.

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 for filling PDF forms but does not explicitly state when to use this tool versus others (e.g., pdf_merger for merging) or when not to use it. It mentions 'local browser processing' as an advantage, but lacks explicit alternative routing.

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