Rasterize a local SVG

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

Annotations mark it as a non-read-only, non-destructive write. The description adds genuine behavioral context beyond that: content refusals, write-and-verify behavior, and the caveat that installed fonts affect appearance. Good disclosure.

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?

Four dense, front-loaded sentences, each adding constraints or behavior. Little waste, though the sizing/codecs phrasing is slightly compressed.

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?

No output schema and 8 params at 25% coverage. The description covers behavior and intent well but does not fully document the sizing (fit/width/height) and quality parameters an agent needs to call it correctly.

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 coverage is only 25%, so the description must compensate. It mentions output formats, intrinsic vs requested box sizing, transparency and JPEG background, but leaves fit enum semantics, width/height, and quality unexplained, so compensation is partial.

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?

Specific verb 'Render' plus resource 'local static self-contained SVG' into named output formats. Clearly a rasterizer, and 'using the existing abox.tools sizing and codecs' distinguishes it from generic siblings like abox_image_convert.

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?

States clear guardrails: only static, self-contained SVGs, refusing active content, animation and external resources. Gives context for when it applies but does not explicitly route to an alternative (e.g. abox_image_convert) for unsupported cases.

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