Save Consistent SVG Icons

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

No annotations are provided, so the description carries the full disclosure burden. It does note the non-destructive default and the returned path/checksum, but omits whether network access is required, what happens for unknown icon identifiers, how files are named, and whether the overwrite flag replaces or merges changed files. For a filesystem-writing tool with zero annotation coverage, that is a meaningful gap.

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 front-loaded sentences with zero waste: the action and scope come first, then the return shape. Nothing is 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 usefully says it returns a path and checksum per icon, closing the main return-value gap. Remaining omissions are error/failure behavior and network requirements, which keep it from a 5.

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 100%; each of dir, icons, height, and overwrite is documented including defaults. The description only echoes the overwrite default already in the schema and adds no meaning beyond it, so the 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: downloading a group of Iconify SVG icons from a single family into a local project folder. The batch/file-write nature implicitly separates it from get_icon and find_icons, but no sibling is named explicitly.

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 batch-persist scope implies when to reach for it, but the description never says when to prefer it over get_icon (single fetch) or find_icons (discovery), nor does it state prerequisites such as family consistency or the 40-icon cap for batching.

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