convert_to_image

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

Substantially augments annotations by detailing: external dependency requirements (Puppeteer, Chrome executable), runtime side effects (transient browser process, CDN fetching), file system behavior (creates parent directories, overwrites existing), and dual return modes (disk write vs JSON binary-guidance). No contradictions with annotations.

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?

Information-dense and front-loaded (purpose first). Length is justified by complexity (browser dependencies, binary output, two return paths). Minor deduction for slight verbosity in implementation details, but structure is logical: purpose → mechanism → prerequisites → side effects → returns → usage guidance.

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?

Excellent coverage given high complexity and missing output schema. Compensates for no output_schema by exhaustively documenting both return variants (JSON confirmation vs base64_preview object), external system requirements, and behavioral side effects. Sibling differentiation is thorough among 24+ conversion tools.

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?

With 100% schema coverage, baseline is 3. Elevated to 4 by adding critical usage context: 'binary format — output_path should almost always be provided' and explaining the conditional return behavior based on output_path presence, neither of which is obvious from schema alone.

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?

Opens with specific verb+resource ('Convert Markdown to a PNG image') and explicitly distinguishes from siblings ('Prefer convert_to_pdf... or convert_to_html'). Clearly defines scope (GFM tables, KaTeX math) and mechanism (headless Chromium).

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?

Provides explicit when-to-use ('when you need a visual snapshot... for embedding in chat, previews, social cards') and named alternatives ('Prefer convert_to_pdf for paginated print output'). Also specifies prerequisites (locally installed Chrome/Edge/Chromium).

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