i_download

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

With no annotations supplied, the description does carry the useful facts that output is SVG text and that color/size are overrides rather than requirements. It does not disclose error behavior for unknown sources, authentication or plan requirements, or whether results are cached — meaningful gaps for a tool with zero annotation coverage.

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?

Four short sentences, front-loaded with the core action and followed by parameter notes and discovery pointers. No sentence is filler; the sibling-tool references double as usage guidance.

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 four-parameter read tool with no output schema, the description covers the return type (SVG text), the two required ids and where to get them, and the optional overrides. It would be complete with a note on failure modes or scope limits (e.g., private/project icons versus global sources).

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%, so all four parameters are already documented with examples and defaults, making 3 the baseline. The description adds only a little beyond the schema: it clarifies that color affects stroke/fill and size affects width/height, and that id comes from search results.

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?

"Download an icon as SVG text from ANY registered source" gives a specific verb, resource, and output format, and the "ANY registered source" phrasing separates it from source-scoped siblings. The one gap is the near-identical sibling i_download_svg, which the description never mentions or contrasts with, leaving an agent to guess which download tool to pick.

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?

It explicitly routes the agent: use i_sources to discover valid source ids and i_search_all to obtain icon ids, which covers the prerequisite workflow for both required parameters. It stops short of stating when NOT to use it (e.g., versus i_download_svg) or what happens on an invalid source/id.

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