svg_to_pdf

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

With no annotations provided, the description carries the burden of behavioral disclosure. It adds a small behavioral detail by specifying the output is 'a PDF page,' indicating a single-page output. However, it does not mention file handling, default naming, or potential limitations, so transparency is moderate.

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 that communicates the essential function without any wasted words. It is front-loaded with the action verb and resource, meeting the conciseness standard perfectly.

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 tool is simple with only two parameters and no output schema. The description provides the core purpose but lacks additional context such as whether the output file is overwritten, what the default output naming is (though that is partly in the schema), or any system dependencies. It is adequate but not thorough.

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?

Although the schema provides descriptions for both parameters, the description of the 'file' parameter in the schema says 'Absolute path to the PDF file,' which is misleading. The tool description clarifies that the input is actually an SVG file, thereby adding critical meaning beyond the schema and preventing a misinvocation.

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 states the tool's function: 'Convert an SVG vector image to a PDF page.' It uses a specific verb (Convert), identifies the input resource (SVG vector image), and names the output (PDF page). This distinctly separates it from sibling conversion tools like png_to_pdf or jpg_to_pdf by explicitly naming 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?

The description implies when to use the tool (when you have an SVG and need a PDF), but it does not explicitly provide comparisons or exclusions relative to siblings. No guidance is given on choosing this over other converters, but the obvious use case is clear from the description.

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