pdf_to_bmp

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the core conversion without mentioning side effects, output file naming, page handling, or whether the tool writes files to disk. The agent is left to infer even basic behavior from the schema.

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 clear sentence that effectively communicates the core purpose without any fluff or redundancy. It is front-loaded with the key information and contains no wasted words.

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?

The tool is a conversion utility, but without an output schema or annotations, the description should explain what the output looks like (e.g., generated BMP files) and any relevant defaults or behavior. It does not, leaving important gaps in context despite the schema covering parameters.

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 provides 100% coverage of all four parameters (file, dpi, pages, output_dir), so the description does not need to add parameter details. However, the description adds no additional semantic value beyond what the schema already exposes, earning the baseline 3.

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 resource ('PDF pages') with a clear output format ('BMP images'). It clearly distinguishes this tool from sibling converters like pdf_to_png or pdf_to_jpg by naming the target format, leaving no ambiguity about what the tool does.

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 choose BMP over other formats, nor any mention of when not to use this tool. The only implied usage is that if you need BMP output, this tool is suitable, but no explicit alternatives or exclusions are given.

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