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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered; the description still adds that the server treats it as read-only and that it "runs straight away" without an approval gate. Because no output schema exists, the enumeration of returned fields (ids, labels, values, types, order, storage watermark) is genuinely useful disclosure.

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?

Two short sentences, front-loaded with purpose and return content. The trailing "Through Royally" clause is slightly awkward filler but does not obscure the definition.

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 carries the burden of describing the return, and it does so by listing the variable attributes. For a zero-required-parameter read-only list tool, nothing essential is missing, though it never says whether results are paged or complete.

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%, so both site_id and include_deleted are already documented, including the soft-delete semantics. The description adds nothing about parameters, so the 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 and resource ("List Elementor Global Variables (design tokens)") and enumerates the fields returned, so the agent knows exactly what it gets. It does not, however, distinguish itself from nearby siblings such as elementor-manage-global-variable or royal-mcp__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?

There is no explicit when-to-use, no exclusion, and no named alternative among the many Elementor/global-settings siblings. The read-only remark hints that no confirmation step is needed, but that is execution behavior rather than selection guidance.

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