heic_to_pdf

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the core conversion, omitting output naming behavior, side effects, quality preservation, or error handling. It also does not correct the mismatched parameter description in the schema.

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?

A single short declarative sentence, front-loaded with the verb and resource. No unnecessary words or repetition; 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?

For a simple conversion tool with complete schema, the description is minimally sufficient, but it lacks annotations and an output schema. It would benefit from clarifying output file naming behavior, potential multi-file handling, and any page-size defaults beyond what the schema mentions.

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?

Schema description coverage is 100%, which normally yields a baseline of 3. However, the schema's 'file' parameter description ('Absolute path to the PDF file') is inconsistent with the tool's HEIC input purpose. The tool description implicitly clarifies the expected input format but adds no direct parameter-level guidance.

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 the action ('Convert') and the specific resource ('HEIC/HEIF photo (iPhone format) to a PDF page'). It distinguishes this tool from sibling converters like jpg_to_pdf or png_to_pdf by naming the exact input format.

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 by naming the HEIC/HEIF format, so an agent can infer when to use it, but there is no explicit 'use this when' or mention of alternatives. In a long list of converter siblings, this provides context but without exclusions.

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