bmp_to_pdf

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'convert' and does not mention side effects, whether the input file is modified, overwrite behavior, or other operational details. This is minimal transparency beyond the raw conversion action.

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, one-sentence statement that is front-loaded and contains no filler. Every word contributes directly to conveying the tool's purpose.

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 straightforward single-input conversion, the description plus schema is mostly sufficient. The output behavior is implied by the schema's output_name description, and the tool's simplicity reduces the need for extensive detail. It does not explicitly mention non-destructive behavior, but that is a minor gap.

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 includes descriptions for both parameters, and the description does not add much beyond clarifying that 'file' is a BMP image. Notably, the schema's 'file' description says 'Absolute path to the PDF file,' which is misleading; the tool description partially corrects this by specifying a BMP input, but it doesn't elaborate further on parameter semantics.

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 conversion: 'Convert a BMP image to a PDF page.' It names the input format (BMP), the action (convert), and the output (PDF page), clearly distinguishing this tool from sibling converters like png_to_pdf or jpg_to_pdf.

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 does not explicitly state when to use this tool versus alternatives, but the BMP-specific wording implies it is the right choice for BMP inputs. No exclusions or alternative recommendations are provided, so it only reaches the 'implied usage' level.

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