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

Annotations declare destructiveHint=true; the description adds real value beyond that by spelling out what is destroyed — alignment, size, colour and tag overrides are released back to global. It stops short of stating irreversibility or permission requirements, but the annotation already carries the safety profile.

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?

A single tight clause, front-loaded with the action ('Put one element back to the global scale') followed by the released properties. No filler; only minor loss is the em-dash list being slightly terse on ordering.

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 destructive mutation with annotation coverage, the description adequately conveys effect but leaves the two required parameters entirely undocumented and offers no prerequisite or permission context. Complete enough to understand intent, not enough to call it safely without the schema.

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% and both parameters (projectId, textKey) are required, yet the description never mentions either. 'One element' loosely hints at textKey but projectId and the identifier format are completely unspecified, so the description fails to compensate for the schema 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?

Names a clear action (put one element back to the global scale) and enumerates exactly which properties are released (alignment, size, colour, tag). This makes the reset semantics distinguishable from a plain style-setter, though it never names the relevant sibling (uichemy_set_text_style).

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?

Usage is implied rather than stated: reverting an element to global-scale styling tells the agent roughly when to reach for it, but there is no explicit when/when-not guidance and no named alternative such as set_text_style for applying instead of clearing overrides.

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