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

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds useful interpretive context about the two key schemes, but says nothing about result shape or pagination beyond that.

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 first sentence is front-loaded and clear. The second is discursive, ending on a convoluted phrase ('stops a change from fighting an existing one') where a plain 'prevents conflicting overrides' would do.

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 sketches what comes back (icons plus their keys under two schemes), but omits the required projectId entirely and gives no sense of result structure. Adequate but with clear gaps.

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?

There is one parameter and schema description coverage is 0%, so the description carries the full burden — yet it never mentions projectId or its format, only discussing the output keys. It does not compensate for the coverage gap on inputs.

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 resource and scope: the icons this project has had replaced, with their override keys. It is identifiable as a read/list operation, though the verb is only implied and it never names the close sibling list_icons or clear_icon_override to sharpen the boundary.

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 supplies conceptual context — that a LABEL and a POSITIONAL id are the two key schemes and that recognizing them prevents conflicting changes — which implies you call this before mutating overrides. But it never states when to use this versus list_icons or how it pairs with clear_icon_override/set_icon.

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