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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely new information by disclosing a 20-credit cost per call, which is not in any structured field. It does not disclose practical limits such as maximum width/height, how remote images inside the markdown are handled, or whether rendering is deterministic.

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 short and front-loaded, but the opening 'Markdown to Image: Markdown to Image converts...' restates the name and title twice before reaching new information. The credit cost is tucked in parentheses at the end rather than being surfaced more prominently.

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 four-parameter rendering tool with a full output schema, the description covers purpose, output formats, and cost, which is most of what an agent needs. The remaining gap is guidance on when to prefer this over the sibling PDF/HTML image 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?

Schema description coverage is 100%, so the schema already explains markdown, width, height, and format, giving a baseline of 3. The description does add some value by enumerating the accepted format values (PNG, JPEG, WebP) even though the schema's format property has no enum, but it says nothing about width/height bounds or default behavior.

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 names a concrete verb and resource ('converts markdown text into visual image representations') and enumerates the output formats, so an agent knows exactly what comes back. It does not, however, distinguish itself from the many adjacent render tools in the sibling list (MarkdowntoPDF, MarkdowntoHTML, HTMLtoImage, PDFtoImage), which an agent could easily confuse it with.

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?

There is no statement of when to use this tool versus the PDF/HTML renderers, and no prerequisites or exclusions. The only contextual signal is the credit cost, which helps a budget-conscious agent but says nothing about tool selection.

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