pdf_add_image

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

Discloses aspect ratio preservation, but lacks details on file overwrite behavior, image size limits, transparency support, or whether the image is embedded/linked. Annotations absent, so description carries full burden.

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 with no fluff. Front-loaded with action, efficient and clear.

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?

Covers main action and one key behavior, but misses behavioral context like file overwriting (outputPath implies new file but not explicit), stacking order, and image size constraints. Adequate but not comprehensive for a 9-param tool with no output schema.

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?

Adds meaning beyond schema by stating aspect ratio preservation and acceptable image formats (PNG/JPG). Schema coverage is 100%, so baseline is 3; description adds further clarity.

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?

Description clearly states verb ('Add'), resource ('image (PNG/JPG)'), and context ('at a position on a page'). It distinguishes from sibling tools like pdf_add_text or pdf_highlight.

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?

Usage is implied for adding an image, but no explicit guidance on when to use this tool vs. alternatives like pdf_stamp or pdf_watermark, and no conditions or exclusions.

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