add_image_stamp_to_pdf

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. While it mentions optional behaviors like opacity, is_background, and show_only_in_print, it does not clarify whether the original PDF is modified or how the output path is used. This is a significant gap for a tool that modifies files.

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 a single sentence that efficiently packs essential information—purpose, required parameters, and optional categories. It is front-loaded with the primary action and remains concise despite covering many parameters.

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 tool's complexity (20 parameters, no output schema, no annotations), the description is incomplete. It does not explain the output format or file handling, and it omits several parameters. The description provides a useful overview but is not sufficient for safe and accurate 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?

The schema has 0% description coverage, so the description must compensate. It explains the purpose of key parameters (pdf_file_path, image_file_path, alignX, alignY) and summarizes optional groups (size, margins, opacity, etc.), but it omits several parameters (image_name, output_file_name, request_doc_name) and uses camelCase names that differ from the schema's snake_case, potentially causing confusion.

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 function: 'Stamp or watermark a PDF with an image' and specifies the API endpoint. It is distinct from sibling tools like add_text_stamp_to_pdf and add_image_watermark_to_image.

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 when to use the tool by listing required inputs and optional parameters, but it does not explicitly state alternatives or when not to use it. The context is present but not fully elaborated.

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