convert_svg

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'Supports multiple output sizes in a single call' as a behavior, but it does not clarify whether existing output files are overwritten, what permissions are required, or how the multiple-size feature is actually invoked—especially since the schema does not reflect it. This leaves significant behavioral gaps.

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 only two sentences, front-loaded with the core action ('Converts an SVG file to PNG, JPEG, or WebP'). The first sentence is efficient and clear. However, the second sentence introduces a capability with no explanation, and because it may be unsupported by the schema, it slightly undermines the conciseness and value of the sentence.

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 description covers the core conversion behavior but omits crucial context: how 'multiple output sizes' is specified, whether output files are overwritten, and any limitations like transparency only applying to PNG. With seven parameters and no output schema, the description should provide more guidance on usage and edge cases to be fully complete.

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?

The schema provides descriptions for all seven parameters, so baseline is 3. The description adds no parameter-level detail, and the claim about multiple output sizes could mislead the agent into expecting a parameter for it, which does not exist. The schema remains the primary source of parameter meaning.

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 explicitly states the tool converts SVG to PNG/JPEG/WebP at specified dimensions, which is specific and distinguishes it from the icon generation and image transformation siblings. However, the claim 'Supports multiple output sizes in a single call' is not backed by the input schema, introducing ambiguity about the tool's actual capability.

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 intended use case is implied: convert SVG files to raster formats. However, there is no explicit guidance on when to use this tool over the sibling tools (generate_expo_icons, transform_image), no exclusions, and no mention of alternatives. The agent must infer usage from the tool name and description.

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