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

Annotations already cover safety (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower, yet the description still adds real behavior: slot labels are authored in templates and readable without a rendered page, and `instances` counts how many icons share a label so a loop-drawn row is replaced as a unit. That is genuine context an agent could not infer from the annotations.

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?

The core purpose is front-loaded, but the middle is a rambling anecdote ('On a project where none have been it answers...') that restates the overrides distinction at length. The useful payload — slot label readability and `instances` semantics — is buried at the end rather than stated crisply up front.

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 must carry return-value meaning, and it does explain what a result row conveys (slot label plus instance count). It is reasonably complete for a read-only listing tool, though it omits pagination or ordering behavior.

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 50% — pageName is documented in the schema as 'One page. Omitted = every page.' while projectId is undocumented. The description says nothing about how to scope by page or what projectId must be, and instead spends its detail on the returned `instances` field, so it does not compensate for the coverage gap.

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 states a specific verb and resource — listing every icon SLOT rendered by pages, including unset ones — and immediately distinguishes that from uichemy_list_icon_overrides, which lists only replaced icons. An agent can pick between the two siblings without opening either schema.

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 names the alternative (uichemy_list_icon_overrides) and the exact condition that selects this tool instead: when no icons have been replaced and there is no id to write to. It stops short of explicit when-not guidance, but the conditional routing is unusually concrete.

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