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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered; the description adds real context beyond that by noting the icon is website-generated, public and marked unreviewed, which tells the agent something about data provenance and quality. It also discloses that the payload includes a dotLottie file URL and a runtime descriptor, which is information no annotation supplies.

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?

It is a single compact sentence with no filler, but it is structured as a colon-separated field dump rather than front-loading the action, and phrases like 'what its motion shows' are vague. It is dense without being efficiently organized.

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 usefully enumerates what comes back (label, originating request, motion summary, dotLottie URL, page, runtime descriptor), which is exactly what an agent needs to decide whether to call it. What is missing is the operation verb and any notion of behavior for a nonexistent or unreviewed id.

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% and the id property already documents its pattern and its source (search_icons), so the description need not compensate. The description adds nothing about the id's format or resolution behavior beyond the schema, making the baseline 3 appropriate.

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 identifies the resource (a community icon) and enumerates its returned fields, but it is a noun phrase with no explicit verb such as 'fetch' or 'retrieve', so the operation must be inferred from the tool name. It also never contrasts itself with the sibling get_icon, leaving the community-vs-standard distinction implicit in the parenthetical alone.

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 statement of when to use this tool versus get_icon or search_icons, and no note on prerequisites or failure modes for an unknown id. The only usage hint, that the id comes from search_icons, lives in the input schema rather than the description.

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