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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety and open-world profile is known. The description adds one genuinely useful trait beyond that — 'best-effort', signaling unreliable results — but says nothing about rate limits, latency, or what form results take.

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 compact phrase with no filler and the core capability front-loaded. It is under-specified rather than bloated, so the terseness costs it little here.

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 burden of explaining return values, and it does not — an agent cannot tell whether it gets icon names, URLs, or rendered assets. For a simple two-parameter tool this is the main remaining gap, and the undefined 'query' parameter compounds it.

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 only 50%: the required 'query' parameter has no description at all, and the description does not compensate by explaining what a query should contain (icon style, keyword, library). Only project_id is documented, and that comes from the schema, not the description.

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 verb ('search') and resource ('icons'), but hedges with 'Suggest icon names / search icons', leaving ambiguous whether the tool returns icon names, identifiers, or image assets. It does not distinguish itself from the adjacent search_photos/search_videos tools, which have nearly identical naming patterns.

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?

There is no explicit when-to-use or when-not guidance, and no named alternative. The parenthetical '(best-effort via web search)' hints that this is a fallback mechanism but never says what it is a fallback to (e.g., web_search or a bundled icon set).

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