convert_svg_to_png

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions determinism, antialiasing, DPI, and alpha preservation, which are useful behavioral traits. However, it omits details like input/output format specifics, error handling, or explicit payment requirements beyond the cost note. It adds some value but lacks comprehensive 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?

The description is a single concise sentence with a parenthetical cost note. It is front-loaded with the core purpose and includes no redundant words. The cost note is informative but not essential to the core function.

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?

The description does not specify the input format (how SVG and DPI are passed in payload) or the output format (PNG file path or binary). Without an output schema, the agent lacks crucial information to correctly invoke the tool. Also, the payment requirement is only implied by the cost note, not explicitly stated. This is insufficient for a tool with no annotations and no output schema.

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 100% with descriptions for both payload and paymentSignature. The description adds no parameter-specific details beyond what the schema provides; it does not explain how to structure the payload or what options are available. Baseline of 3 applies due to high schema coverage.

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 identifies the tool as an SVG-to-PNG rasterizer with specific features (determinism, antialiasing, DPI, alpha preservation). It distinguishes itself from sibling tools like convert_gltf_to_obj or generate_qr_code_svg by naming the exact conversion format.

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?

No explicit guidance on when to use this tool versus alternatives. It does not mention alternatives, exclusions, or conditions for use. The description implies usage for SVG to PNG conversion, but this is not stated as a recommendation or contrasted with other conversion tools.

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