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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The closing line "its server marks it read-only, so it runs straight away" mostly restates those hints, though it usefully confirms no confirmation step is required. Nothing is disclosed about payload size, caching, or permissions, so it sits at additive-but-thin.

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 short sentences with the resource and returned contents front-loaded. The trailing Royally-specific read-only note is slightly wasteful given the annotations already say the same thing, but it costs little.

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 enumerates the returned token categories, which is exactly what an agent needs before calling. The remaining gap is disambiguation from sibling global/kit-settings tools, which the description never addresses.

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 only one parameter (site_id) and schema coverage is 100% with an enum and site URL documented inline. The description adds nothing about it, which is acceptable given the schema already carries the full meaning.

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 ("Returns the active Elementor kit/global settings") and enumerates the contents: colors, typography, spacing, breakpoints. It does not, however, distinguish itself from closely related siblings such as emcp-tools-get-settings, emcp-tools-list-global-classes, or royal-mcp__elementor_get_kit_globals, so an agent must infer 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?

The description explains what the values are ("site-wide design tokens used across all pages") but never says when to reach for this tool versus get-settings or the Elementor kit-globals sibling, nor any prerequisite. Usage is only inferable from the payload description.

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