Pdf To Images

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

Without annotations, the description carries the behavioral burden, and it does disclose return cardinality ('one image per page') and that the volume sent to a model can be bounded. It doesn't cover resource cost, failure behavior on unsupported or corrupt files, or default page cap, so it is incomplete but substantive.

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 verb and the output, and the second sentence routes straight to the relevant parameters. Nothing redundant.

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 six-parameter tool with no annotations and no output schema, the definition is close to sufficient: format, per-page cardinality, and page-limiting controls are all covered. It stops short of mentioning default output volume or resolution implications, and with no annotations the safety/cost profile 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%, so the schema already names and constrains every parameter (dpi range, page bounds, max_pages cap, max_width). The description only gestures at first_page/last_page/max_pages as limiting controls, which is baseline-level added value at this coverage.

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 and resource (render document pages to images) and frames the purpose around vision models, which tells an agent exactly when this output format is appropriate. No siblings exist, so differentiation isn't required.

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 says what the images are for ('for vision models') and points at three parameters for limiting volume, which implies usage context. However, it gives no when-not-to-use guidance or scope limits (e.g., at what point to prefer text extraction instead), so this is implied rather than explicit guidance.

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