Get a Hugeicon as SVG

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

Annotations declare readOnlyHint=false, and the description explains why: it can write an .svg file, with an explicit note to use an absolute path and an overwrite flag in the schema. That reconciles the non-read-only hint. It stops short of describing failure modes (e.g. write errors, path rejection).

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 sentences, no waste, with the primary return value front-loaded and the optional side effect second. Nothing redundant.

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?

With no output schema, the description correctly identifies the return value as SVG markup and covers the main side effect. For an 8-parameter tool it leans on the rich schema, which is reasonable, though a note on what happens when save_to is combined with style/color would complete it.

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 coverage is 88%, so the schema already documents nearly every parameter including defaults and constraints. The description adds only the 'chosen style' and 'absolute path' framing, both of which the schema states more precisely, so baseline 3 applies.

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 specific verb and resource ('Returns one icon as SVG markup in the chosen style'), which clearly distinguishes retrieval from siblings like search_icons and list_styles. It doesn't explicitly name those siblings, keeping it short of a 5.

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 by the optional file-write example ('for example to upload into Figma'), but it never states when to prefer this over search_icons or list_styles. The schema's name parameter does point back to search_icons, which carries some of that load.

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