retrieve_icon

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

With no annotations provided, the description carries the behavioral disclosure burden. It does state that the result is the icon source in SVG format, but it does not clarify whether the response is raw SVG markup, a URL, or a file object, nor how unknown or invalid icon names are handled.

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?

A single, front-loaded sentence with no filler. It communicates action, target, and format efficiently, and every word earns its place.

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?

Adequate for a simple one-parameter retrieval tool, but incomplete without an output schema or more precise return-format details. The agent is left to guess what 'source in SVG format' means concretely and how icon names should be specified.

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%, and the only parameter, 'name', already has a clear 'Icon name' description. The tool description adds no further semantic detail about naming conventions, accepted formats, or possible values, so the schema remains the primary source of parameter meaning.

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 names a specific action ('Retrieves'), a specific resource ('the icon'), and a distinguishing output trait ('source ... in SVG format'). This plainly separates it from siblings list_icons and search_icons, which operate over icon collections rather than fetching a single icon's source.

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?

No guidance is given on when to choose this tool over list_icons or search_icons. There are no exclusions, prerequisites, or alternative-selection cues, so the agent must infer usage from the tool name and sibling context.

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