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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), and the description adds genuine behavioral detail beyond them: results are identifiers in 'prefix:name' form with no SVG payload, and a clickable grid is surfaced to the user when the client supports it. That UI side effect is exactly the kind of trait annotations cannot express.

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 sentences, front-loaded with purpose and return shape, then workflow advice and UI behavior; each sentence carries distinct information. Slightly dense but no filler, and nothing important is buried.

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 read-only search with no output schema, the description covers what the agent needs: what is searched, what is returned (and what is not), how to obtain the actual files, and the user-visible picker behavior. Safety is handled by annotations, so no gap remains.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning: it explains the 'prefix:name' shape that the prefix parameter scopes and that prefix/name compose the download URL, tying the parameters to the return format and a follow-up action. This goes beyond the schema's one-line parameter descriptions.

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?

States a specific verb (Search) and resource (open-source SVG icons and brand logos) with clear scope (hundreds of icon sets, by keyword). It implicitly separates itself from get_icon by noting it returns names and no SVG content, but it never names a sibling, so an agent must infer the boundary with find_brand_logo, whose territory ('brand logos') this description claims.

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?

Gives concrete when-to-use context (keyword search over many sets) and an explicit when-not alternative: for bulk file saving, hit the i.allsvgicons.com URL directly rather than loading icons into context. It stops short of routing the agent to get_icon or find_brand_logo for single-icon or brand-logo lookups.

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