pdf_to_png

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

No annotations are present, and the description offers no behavioral details such as output file naming, handling of multiple pages, default DPI, or behavior when output_dir is omitted. It only states the basic functionality without disclosing important behavioral traits.

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, direct sentence that front-loads the main purpose. It is not verbose and earns its place, though its brevity leaves out crucial context that would require expansion.

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 conversion tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain the output format specifics (e.g., one PNG per page, file naming) or provide usage context relative to the many sibling converters.

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 schema already documents all 4 parameters with descriptions (100% coverage), so the description does not need to add parameter details. However, it also does not clarify any parameter interplay or output behavior beyond what the schema provides, so the baseline of 3 is appropriate.

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 'Render' and clearly states the input (PDF pages) and output format (PNG images), distinguishing it from sibling tools like pdf_to_jpg or pdf_to_tiff. It is a clear, specific verb+resource+output statement.

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?

No guidance is provided on when to use this tool versus alternative conversion tools. It neither mentions exclusions nor recommends scenarios where this tool is preferred over its siblings.

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