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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds meaningful nuance beyond that by disclosing the blast radius — only auto-matched icons change, hand-picked ones are untouched — which is exactly the kind of context an agent needs before mutating site-wide styling.

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?

Two short sentences with no filler; the scope and allowed values are front-loaded, and the exclusion of hand-picked icons follows immediately as the qualifier.

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 two-parameter mutation tool with no output schema, the description covers what changes and what is protected. Minor gaps remain: it doesn't say whether the change takes effect immediately or requires a publish step, and projectId is undocumented.

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 compensate. It does spell out the style values ('outline or filled'), which maps to the enum, but projectId is left completely unexplained in both the schema and the description.

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 names a specific setting (site-wide icon style for auto-matched icons) and enumerates the two allowed values, outline or filled. It also implicitly separates this tool from per-icon siblings such as set_icon by noting that hand-picked icons are left 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?

It gives clear scope context: one choice applies to the whole site, and manually chosen icons are excluded. However, it never names an alternative tool (e.g. set_icon or clear_icon_override) or states when a caller should prefer this global setting over per-icon control.

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