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

Annotations already declare readOnlyHint and closed-world, and the description adds real behavioral detail beyond them: default icon dimensions, the listing fallback when names are omitted, and the 'missing:' sentinel for unknown names. The recovery instruction (follow Icon and nav in components.md, never an emoji) is unusually useful guardrail context.

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 purpose. However the phrasing is telegraphic ('Missing names come back as missing:') and the trailing components.md instruction is compressed to the point of ambiguity about what 'nav' means.

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 does explain the return shape (SVG), the list mode, and the missing-name sentinel. It still leaves gaps on output ordering, whether results are grouped, and how group and names interact, which matters for a two-parameter lookup tool.

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%, so the description must carry parameter meaning. It explains 'names' (lookup by name) and that 'group' drives the listing mode, but it never states whether group also filters when names are supplied, nor what a group string should look like.

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?

Names the resource (Lounge Icons), the return format (SVG), and the lookup key (by name), plus concrete rendering defaults (24px, stroke 1.75). It is clearly distinguishable from siblings like get_piece or browse_library, though it never explicitly contrasts with them.

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?

The no-names case is covered ('lists them by group'), so the agent knows two modes of invocation. There is no guidance on when to use this versus browse_library or get_piece, and no statement of what happens in the group+names combination case, so the agent must infer.

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