convert_icon

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

No annotations are provided, so the description carries the full behavioral burden. It reveals the underlying library (Sharp) but says nothing about whether conversion fails on malformed SVG input, what happens when fromFormat does not match the actual iconData content, whether the result is returned inline or written somewhere, or any size limits — all material for a conversion tool.

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?

Two short sentences, purpose front-loaded, no filler. The second sentence is thin but not wasted, since custom sizing is a real capability of the tool.

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 4-parameter conversion tool with no annotations and no output schema, the description should explain return behavior and format-mismatch handling. It instead repeats a size capability already documented in the schema and misstates the conversion direction, leaving key operational questions unanswered.

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 50%: size and iconData are documented, but fromFormat and toFormat have no descriptions at all. The description's "Convert SVG icon to PNG" actually conflicts with the parameter semantics by implying a fixed direction, and it adds no meaning about the enum values or whether fromFormat is validated. With low coverage the description should compensate and does not.

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?

States a concrete verb and resource ("Convert SVG icon to PNG") and names the implementation library, which is more than a tautology. However, it narrows the tool to SVG→PNG while fromFormat/toFormat enums permit svg and png in either direction, so the stated purpose undersells and mildly misdescribes the actual scope. It also gives no signal to distinguish it from siblings like optimize_svg or create_sprite.

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?

There is no statement of when to reach for this tool versus optimize_svg, create_sprite, or get_icon. The only usage hint is "Supports custom sizes," which is a capability claim, not guidance on selection or preconditions.

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