aaddyy_image_to_pdf

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

With no annotations at all, the description carries the full burden. It does disclose real behavioral traits — the 1–20 image range, one page per image, accepted formats — but says nothing about authentication, whether the result is a URL or binary file, synchronous vs. async behavior, or any size limits.

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?

Three short sentences, front-loaded with the action and result, then the page-mapping rule, then format support. 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 or annotations to lean on, so the description must stand alone. It covers purpose, image count and formats adequately, but leaves the input encoding of 'images' and the delivery format of the resulting PDF unspecified — gaps an agent cannot resolve from the structured fields.

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?

The single required parameter 'images' is typed only as a string with 0% schema description coverage. The description never explains how multiple images are supplied in one string value (URLs, comma-separated list, base64, JSON array?), which is the critical detail for invoking this tool correctly.

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 concrete verb and resource ('Convert ... images into a single downloadable PDF document') plus scope constraints (1–20 images, one image per page, supported formats). It is clearly distinguishable from a generic converter, though it never explicitly contrasts itself with the sibling pdf_merge, which an agent might reasonably confuse it with.

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?

There is no when-to-use guidance and no mention of the obvious alternative (aaddyy_pdf_merge). The 1–20 image cap hints at a boundary but the description never says what to do above that limit or when to pick a different tool.

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