rasterize_pdf

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

The description discloses the core behavior but not the operational details. It doesn't specify whether the output replaces the input, whether it creates new files, what image format is produced, or any side effects. With no annotations, this minimal description leaves significant behavioral uncertainty.

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 only one sentence, which is concise, but the 'and back' phrase is confusing and lacks necessary clarity. It earns a middle score because while brevity is positive, the content is slightly misleading and under-specified.

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?

With no output schema and no annotations, the description must explain return values and side effects. It does neither. The ambiguity around 'and back' and lack of details about output format or behavior makes the tool underdocumented for a conversion task among many similar siblings.

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 input schema has 100% coverage for all three parameters, providing clear descriptions for dpi, file, and output_name. The tool description adds no additional parameter context, so the schema carries the full burden, warranting the baseline score.

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 states a specific action ('rasterizes vector content') but the phrase 'and back' is ambiguous, suggesting bidirectional conversion that contradicts the tool's name. It doesn't clearly distinguish from sibling tools like pdf_to_png or pdf_to_jpg, which also convert PDF pages to images.

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 on when to use this tool versus the many sibling conversion tools. The description implies a use case (rasterizing vector content) but does not state alternatives, prerequisites, or typical scenarios.

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