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

Annotations only provide readOnlyHint=false, openWorldHint=false, and destructiveHint=false, so the description carries most of the behavioral burden. It explains the core transformation (rasterization) and mentions output format choices, but does not disclose side effects, output return details, or behavior when width/height are zero. The schema covers edge cases like invalid DPI values, so the description adds some but not rich behavioral context.

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 focused sentence that front-loads the action and output format, then lists the adjustable options. The [category: photo] tag is a useful, compact classification. There is no wasted text.

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 six parameters and no output schema, the description is reasonably complete: it names input type, output formats, and key controls. The schema covers parameter details. It does not mention return behavior or potential side effects, but the core decision-making information for an agent is present.

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 the parameters are already fully documented. The description restates the concept of resolution, DPI, and background color without adding new meaning beyond what the schema provides. This meets the baseline but does not exceed it.

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 states a specific action ('Rasterize an SVG vector file to PNG') and names the target formats (PNG, JPG, WebP) plus key options (resolution, DPI, background color). It clearly identifies the tool's resource and distinguishes it from general converters like photo_format_converter by specifying SVG as the input.

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 the primary use case: converting an SVG vector file into a raster image. It does not explicitly name alternatives or exclusion conditions, but the title and phrasing make the intended context clear enough for an agent to select it over sibling tools.

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