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

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description's main added value is the explicit cost (10 credits), which helps an agent decide whether to call it. It says nothing about size limits, upload mechanics, or processing latency, so it is adequate but not rich.

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 first sentence redundantly restates the tool name and title ('SVG Converter: SVG Converter is...'), wasting the front-loaded position. The remaining sentences are efficient and informative, but the opening duplication weakens structure.

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?

An output schema exists, so return values need no explanation, and the five-parameter tool is simple. The description covers formats and cost, but leaves a gap on how the SVG input is supplied (URL vs. upload), which matters for correct invocation.

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 100%, so all five parameters including quality, maxWidth, maxHeight, and outputFormat are already documented. The description adds no meaning beyond the schema—for example, it does not clarify whether 'image' expects a URL, base64 blob, or file reference, despite only saying 'Upload an SVG file'.

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?

Uses a specific verb and resource: transforms vector SVG into raster PNG, JPG, or WebP, and names concrete artifact types (logos, icons, illustrations). It distinguishes itself by input format (SVG) from generic siblings like ImageConverter or HEICConverter, but never names those siblings explicitly.

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?

Provides a use context ('for use in applications that don't support vector graphics') which implies when to use it. It gives no explicit when-not conditions, no prerequisites, and does not route the agent to alternative converters (ImageConverter, WebPConverter, HTMLtoImage) that could overlap.

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