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

With no annotations, the description carries the burden of behavioral disclosure. It adds the 'browser-based' trait, which hints at client-side processing and possible privacy benefits, but it does not explain behavior like page-range handling, output resolution, or file-size limits. It gives some insight but leaves significant behavior unspecified.

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 sentence with a parenthetical note, packing the key information (what it does, output formats, quality, and platform) into just 10 words. Every word earns its place, and it is front-loaded with the primary action.

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 simple tool with no parameters and no output schema, the description is mostly sufficient, but it lacks important details such as whether all pages are converted or just one, and what the return format is (e.g., download links, base64). These gaps could lead to incorrect agent expectations. Some additional context would round out the description.

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 is empty (0 parameters), so the baseline is 4. The description adds value by naming output formats (PNG, JPEG, WebP), which are the only configurable aspects, even though they are not formal parameters. It adequately communicates everything an agent needs to know about the tool's inputs.

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 clearly states the tool converts PDF pages to PNG, JPEG, or WebP with high quality. The verb 'convert', the resource 'PDF pages', and the output formats specifically define the tool's function, distinguishing it from sibling tools like pdf-to-word or image-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 provides clear context for when to use the tool: when you need PDF pages as image files. It does not explicitly mention alternatives or exclusions, but the output formats make the use case obvious among the many PDF-related sibling tools, so it offers adequate guidance without needing to name alternatives.

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