import_icon

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

With no annotations, the description carries the full burden of behavioral disclosure. It does mention 'Never overwrites files,' which is a useful safety guarantee, but it fails to explain what happens on file conflict (skip vs error), whether it modifies configuration files like pubspec.yaml, or whether network access is required. This is a significant gap for a write operation.

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?

The description consists of two focused sentences. The first states the core action and target platforms; the second adds a critical safety guarantee. Both sentences earn their place, with no wasted words.

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?

Given the tool has 5 parameters, 0% schema description coverage, no annotations, and no output schema, the description is far too sparse. It lacks explanations for parameters, conflict handling, and usage context. While it covers the basic purpose, it does not provide enough information for an agent to invoke the tool correctly in all scenarios.

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 0%, and the description provides no parameter-level semantics. It does not explain 'name', 'root', 'style', or 'registerFlutterAsset'. The target parameter is only loosely implied by the phrase 'Android, Flutter, or SVG project assets' but not explicitly tied to the schema field. The description adds almost no value for parameter understanding.

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 clearly states the action ('Download an official icon') and the target destinations ('Android, Flutter, or SVG project assets'). It distinguishes import_icon from sibling tools like delete_icon, search_icons, and update_icon by focusing on the import/download aspect.

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 explicit guidance is given on when to use this tool versus alternatives. The description does not mention that search_icons should be used to find icons first, nor does it exclude cases where update_icon or delete_icon would be more appropriate. The usage context is only implied by the action.

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