pdf_embed_qr_code

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

Annotations already declare idempotentHint=true and destructiveHint=false. The description adds value by listing supported barcode symbologies but omits file handling behavior (whether outputPath can match filePath, overwrite behavior) and coordinate system quirks that could affect placement accuracy.

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 efficiently structured sentences with zero waste. The first establishes the core operation and location; the second enumerates supported formats. Information is front-loaded and appropriately sized for the tool's complexity.

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 100% schema coverage and safety annotations, the description is nearly complete. Minor gap: it does not clarify whether the operation preserves the original file (implied by separate outputPath but not stated) or behavior when coordinates exceed page boundaries.

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 baseline is appropriately 3. The description lists the barcode types (already in the enum) but does not add syntactic guidance, validation rules, or semantic context beyond what the schema provides for the 8 parameters.

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 action ('Embed'), target resource ('QR code or barcode'), and placement method ('into a specific page...at given coordinates'). It effectively distinguishes from sibling pdf_embed_image by specifying scannable code types rather than general images.

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 lists supported barcode formats, which implicitly signals when to use the tool, but lacks explicit guidance on when to choose this over pdf_embed_image or prerequisites like file existence requirements. No alternatives or exclusions are mentioned.

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