png_to_pdf

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Convert' and 'single PNG' but does not disclose behavior such as whether the output file will overwrite existing files, what the default output name and location are (though partially in schema), or any limitations beyond single-image support. For a conversion tool, this is minimal transparency.

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 a single, front-loaded sentence with no redundant words. It efficiently states the core function and the key qualifier 'single' in a concise manner.

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 this might seem sufficient, but the description lacks important context: it does not clearly specify the input format (the name implies PNG, but the schema says PDF), does not explain output behavior (e.g., default output naming, overwriting), and with no annotations or output schema the description is the only source of behavioral context. The schema error makes it incomplete and potentially confusing.

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%, so the baseline is 3, but the schema itself is misleading: the 'file' parameter is described as 'Absolute path to the PDF file' for a PNG-to-PDF tool. The description does not correct or clarify this error, nor does it add meaningful semantics for 'output_name' beyond what the schema already states. The mismatch between the tool's purpose and the parameter description significantly undermines parameter understanding.

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 uses a specific verb ('Convert') with a clear resource ('a single PNG image') and result ('to a PDF page'), making the tool's purpose unambiguous. It also distinguishes from sibling tools like jpg_to_pdf or tiff_to_pdf by explicitly naming the PNG 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?

The description clearly implies when to use: when you have a single PNG image that needs to become a PDF page. However, it does not explicitly mention alternatives or exclusions, such as using image_to_pdf for multiple images or batch conversion. The context is clear but lacks explicit guidance on choosing among conversion tools.

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