Embed image in PDF

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

Annotations already indicate idempotentHint=true, so the description's statement about generating a PDF does not contradict. The description adds some behavioral context (accepts base64, supports options) but does not disclose potential side effects, authorization needs, or limitations like file size. It is adequate but not rich.

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 two sentences totaling 32 words, front-loaded with the core purpose. Every word earns its place; there is no redundancy or fluff. It is highly concise and well-structured.

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 (9 parameters, 3 required, output schema exists), the description covers the main input format, optional features, and basic behavior. It could mention output format or PDF/A compatibility explicitly, but the schema and annotations fill some gaps. It is complete enough for an AI agent to understand the tool's purpose and basic usage.

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 description coverage, the input schema fully documents all 9 parameters. The description only mentions 'optional caption and custom render dimensions,' which adds minimal value beyond the schema's detailed parameter descriptions. Baseline of 3 is appropriate.

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 verb ('generate'), resource ('PDF document with embedded image'), and scope ('JPEG or PNG, base64-encoded, optional caption and custom render dimensions'). It effectively distinguishes from sibling tools like add_attachment or add_barcode by focusing on embedding an image directly into the PDF.

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 this tool (embedding an image as part of a PDF), but it does not provide explicit guidance on when not to use it or direct comparisons to alternatives like add_attachment. The context is clear, but lacks exclusionary or alternative recommendations.

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