Convert HEIC to JPG

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

Annotations already declare openWorldHint=true and destructiveHint=false, and the description usefully confirms the external-service behavior ('uploaded to conv2pdf') plus the cost model ('counts as one conversion') — quota/billing context the annotations do not convey. It does not restate the non-overwrite guarantee, but that detail lives in the output_path 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?

Two short sentences, front-loaded with the conversion and followed by the context an agent needs (upload destination and quota impact). No filler or redundancy.

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?

There is no output schema, but the description plus the rich output_path schema make the return contract clear (result written to a path). The quota disclosure covers the main hidden cost; only the upload/network-failure behavior is left unstated.

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% with only two parameters, both well documented (path resolution rules, default output naming, no-overwrite guarantee), so the baseline of 3 applies. The description adds no syntax or format detail beyond the schema.

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?

States a specific verb (converts) and precise resource (iPhone HEIC or HEIF photo to a JPG image), which is enough to separate it from the PDF-centric siblings like convert_to_pdf and convert_pdf_to_images. It stops short of naming any sibling explicitly, but the transformation pair is unambiguous.

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 only implied: 'an iPhone HEIC or HEIF photo' tells the agent the input class, but there is no when-to-use, when-not-to-use, or pointer to an alternative converter. Adequate for a narrow single-purpose tool, but the agent gets no routing guidance.

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