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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known; the description adds the site-wide blast radius and the fact that design:null reverts badges to their layout defaults, which is genuinely useful. However it never says whether omitted fields are left unchanged, whether the change is reversible, or that it overwrites existing site-wide styling everywhere.

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?

Three tight sentences that lead with the scope and the affected panel, then the sibling distinction, then the reset behavior. Dense and free of boilerplate, though the final clause about null sits after the sibling reference rather than with the design explanation.

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?

No output schema exists, yet the description makes clear what is affected (every badge site-wide) and what a reset does, which is the essential return-side context. The main omission is partial-update semantics — whether supplying only projectId plus one field leaves the others untouched — for a destructive site-wide mutation.

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?

With only 20% schema description coverage, the description does the heavy lifting for the most opaque parameter: it decodes design as '1 Outline · 2 Solid · 3 Soft · 4 Dot · 5 Underline' plus the null semantics, which the schema's bare integer range does not convey. size (S/M/L) and displayIcon (Yes/No) are self-evident enums and radius is already described in the schema, so remaining gaps are minor.

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 and resource ('the site-wide badge look — the Style Guide's Badges panel') and enumerates the exact aspects controlled: size, corner radius, icon display, design. It explicitly contrasts with uichemy_set_badge_design, so the agent can separate site-wide styling from single-badge overrides 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?

'uichemy_set_badge_design overrides ONE badge on top of this' gives a clear routing rule between the two related tools, and the null-clears note explains a reset case. It stops short of stating negative conditions (e.g. when not to touch the style kit at all) or prerequisites, so it's strong but not fully explicit.

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