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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds genuinely useful context beyond these: it returns files as text rather than writing them ('It writes no files'), which prevents an agent from assuming an install actually mutates the filesystem despite the 'install' name.

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?

Three short sentences, front-loaded with the core action and output shape, and closed with the two most important caveats (no file writes, parameter provenance). No sentence is wasted.

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 carries the return-value burden and does so adequately by describing the component-per-icon files and barrel index. It is slightly incomplete in that it only describes the tsx return shape and doesn't note the svg alternative, though the schema covers the format parameter.

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 every parameter (names, format, variant, libraryId, targetDir) is already documented with meaning and examples. The description references libraryId and names but adds no syntax, defaults, or format nuance beyond the schema, 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?

The description states a specific verb and resource ('Fetches the named icons from the public Iconify API') and details the exact output (one React component file per icon plus an index.ts barrel, as text). It also distinguishes itself from siblings by naming find-icons as the source of the names, clarifying that this is a preparation step rather than a search or write.

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 provides clear workflow context by stating it takes a libraryId and icon names 'from find-icons', which routes the agent to the upstream tool. It doesn't state explicit when-not conditions or name alternative installers, so it stops short of a full 5.

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