Render SVG to PNG

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

No annotations provided; description discloses side effects: returns PNG inline and writes a .preview.png file. Lacks details on overwriting behavior but sufficient for basic transparency.

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?

Two sentences with no redundancy; front-loaded with action and 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 simple 3-param tool without output schema, covers return format (inline) and side effect (file creation). Could specify output type precisely but adequate.

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 has 0% description coverage; description only mentions svg_path implicitly. Does not explain width and scale parameters, leaving the agent uncertain about their effect.

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?

Clearly states verb 'Rasterize' and resource 'SVG to PNG', with purpose 'visual verification'. Distinct from siblings like convert_image_to_svg (opposite), edit_svg, import_vector, inspect_svg, optimize_svg.

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?

Implies use for visual verification via 'for visual verification', but no explicit when-to-use/exclusions/alternatives. Could be improved with contrast to siblings.

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