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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description then adds genuine value on the dimension annotations cannot cover: with no output schema, it enumerates what comes back (states, styles, weights, motions, dotLottie URL and hash, install commands, and platform snippets). It omits error behavior (e.g. unknown id), which keeps it below 5.

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 zero padding, leading with the payoff ('everything needed to use one icon') before the itemized contents. Slightly list-like rather than explanatory, but nothing is wasted.

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 one-parameter read tool with strong annotations, the main missing pieces are how it relates to search_icons and get_community_icon and what happens when an id is not found. The absence of an output schema is partly compensated by the returned-content enumeration, so it is adequate but not complete.

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?

Only one parameter, and schema coverage is 100% with format and example ('trash', from search_icons) already documented in the schema. The description adds no additional meaning about the id beyond what the schema provides, so the baseline 3 applies.

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 makes clear this retrieves full detail for a single icon ('Everything needed to use one icon') and enumerates exactly what that detail includes. It does not differentiate from the sibling get_community_icon, which an agent could plausibly confuse it with, so it falls short of a 5.

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?

Usage is only implied: the 'everything needed to use' framing suggests this is the follow-up step once an icon has been chosen, and the schema hints at coming 'from search_icons'. No explicit when-to-use, when-not-to-use, or sibling routing (search_icons vs get_community_icon) is given.

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