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

Annotations already carry readOnlyHint=false and destructiveHint=false, so the safety baseline is set. The description adds the meaningful behavioral concept of rasterization and optional output formats, but it does not disclose side effects, output delivery, or whether the original file is preserved, which would add further 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 compact sentence that front-loads the action and output format, then summarizes the adjustable options. The '[category: photo]' suffix is small and doesn't add clutter. Every word earns its place.

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 6-parameter conversion tool with a fully descriptive schema, the description captures the core purpose, output options, and key customization dimensions. It doesn't spell out return-value behavior, but no output schema exists and the converted raster file is strongly implied; explicit sibling differentiation would be the only notable gap.

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%, and each parameter already has a detailed explanation, including the dpi string-coercion warning and jpg transparency behavior. The description only summarizes 'resolution, DPI, and background color' without adding new parameter-level meaning, so it sits at the baseline for 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 uses a specific verb ('Rasterize') plus a clear resource ('SVG vector file') and output ('PNG (or JPG/WebP)'), and names the key options (resolution, DPI, background color). This clearly distinguishes it from generic sibling tools like photo_format_converter by emphasizing the SVG-vector-to-raster workflow.

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?

Usage is implied: use this when an SVG needs to become a raster PNG/JPG/WebP. However, the description does not explicitly state when to prefer this over alternatives such as photo_format_converter or convert_file, nor does it give exclusion criteria, so the agent must infer routing from the tool name and wording.

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