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

readOnlyHint=true already covers the safety profile, so the description's real addition is the return-behaviour detail that colours are pre-converted to currentColor for mono/duotone. That is genuinely useful, but it says nothing about error behaviour for an unknown id, whether removed icons 404, or caching. Adequate but thin beyond the annotation.

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?

Purpose is front-loaded in the first clause and the whole thing is three short sentences. The mid-sentence aside about blocks calling fabrement_icon and the oddly formatted 'Rules:' line cost a little clarity, but there is no padding.

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 well to say an SVG comes back with currentColor applied, and it points at the contract doc for the rest. Still, it leaves the agent uninformed about failure modes and about the practical step of getting a valid id, which list-icons (a sibling) presumably provides.

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 the single id parameter exists and schema coverage is 100%, with the schema itself documenting '<group>/<slug>, from list-icons.' The description repeats the id shape via fabrement_icon('<id>') but adds no format or lookup detail beyond the schema. Baseline 3 applies when the schema carries the parameter documentation.

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+resource: fetching one library icon together with its SVG, which cleanly separates it from the sibling list-icons (plural, enumeration) and the save-icon/delete-icon mutations. The 'as the site renders it' phrasing adds a rendering-pipeline qualifier that helps scope it, though the aside about a block calling fabrement_icon is about a different surface and slightly muddies the subject.

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 an explicit prerequisite ('get-skill-doc {id:"icons-contract"} — read it before the first call') and an implicit when-not ('A block does not paste this: it calls fabrement_icon'). It never routes to list-icons for discovering ids or to delete-icon, but the context and prerequisite are clear enough to act on.

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