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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds the useful operational note that the server marks it read-only so it runs without approval, plus the breakpoint/state resolution behavior, but the repeated "Read-only" adds nothing new.

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?

Purpose and mechanics are front-loaded in the first two sentences, with the parameter guidance immediately after. The closing "Read-only. Through Royally..." sentence partly repeats information already conveyed by annotations, slightly diluting the density.

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 simple two-parameter read tool with no output schema, the description adequately covers what it returns (names plus CSS properties per breakpoint/state) and how to scope the query. Only the precise response shape is left implicit, which is acceptable given the tool's simplicity.

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 100%, and both parameters (site_id enum, class_ids array) are fully documented in the schema with an example. The description restates the class_ids behavior (omit to return all) but adds no format or edge-case detail beyond the schema, so baseline 3 applies.

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+resource (resolves Elementor Class Manager / Global Classes entries) and explains the transformation performed: mapping opaque "g-" IDs to human-readable names and CSS properties per breakpoint/state. That is clearly distinct from sibling listing tools like elementor-list-variables or elementor-get-kit-globals.

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?

Gives a concrete use case ("Use it to understand what styling a g- class applies") and the selection rule for parameters (pass class_ids for specific IDs, omit to list all). It stops short of naming an alternative tool or stating when not to use it, so it falls just below the top band.

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