export_png

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

Annotations only provide destructiveHint=false. The description adds useful behavioral context by noting Inkscape as the execution engine and promising 'bounded, allowlisted options', which helps set safety expectations. However, it does not explain side effects, revision handling, overwrite behavior, or output semantics.

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 efficient sentence with no redundant wording. It front-loads the core action and adds the Inkscape and bounded-options qualifiers without wasted space.

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 tool with 12 parameters, 4 required, and 0% parameter documentation, this description is far too sparse. It does not explain what expectedRevision is, how outputPath behaves, or how the sizing and background options interact. The output schema reduces the need to document return values, but invocation semantics remain mostly unexplained.

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 0%, yet the description names none of the 12 parameters. It does not clarify how dpi, area, width, height, background, expectedRevision, or outputPath should be set. The phrase 'bounded, allowlisted options' is too generic to count as parameter guidance.

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 uses a specific action verb ('Exports'), names the source resource ('SVG document'), the target format ('PNG'), and the mechanism ('through Inkscape'). This clearly distinguishes it from sibling tools like export_svg and export_pdf.

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?

The PNG/SVG pairing implies when the tool should be used, but the description does not explicitly state when to prefer it over alternatives such as export_svg or export_pdf. There are no exclusions or conditions provided.

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