pdf_embed_image

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

Adds valuable behavioral context beyond annotations by describing 'aspect ratio preservation' and 'custom positioning' semantics. Annotations already cover safety (idempotent, non-destructive), but description could clarify that it creates a new file rather than modifying in-place.

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 zero waste. Front-loaded with core operation (embedding), followed by key capabilities (positioning/scaling). Every word earns its place.

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?

Sufficient for an 8-parameter mutation tool with complete schema and annotations. Covers core operation and key features. Minor gap: could explicitly state that outputPath creates a new file rather than altering the source PDF in-place.

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?

With 100% schema coverage (baseline 3), the description adds semantic framing by mapping 'custom positioning' to x/y parameters and 'optional scaling with aspect ratio preservation' to width/height interactions, enhancing understanding of how parameters interact.

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?

Specific verb ('Embed'), specific resource ('PNG or JPEG image into a specific page of a PDF'), and distinguishes from sibling pdf_embed_qr_code by explicitly limiting input to PNG/JPEG formats rather than QR codes.

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?

Provides implied usage guidance by specifying supported image formats (PNG/JPEG) and capabilities (positioning, scaling), but lacks explicit when-to-use guidance or named alternatives compared to siblings like pdf_embed_qr_code.

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