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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds context beyond them: it requires read_post on the parent post_id, and it documents the failure path ('returns found=false with the count of elements searched') for diagnosing bad IDs. It does not discuss payload size or performance for large elements, which is the remaining behavioral gap.

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?

The core purpose and return fields are front-loaded and every substantive sentence earns its place. Minor clutter comes from the bracketed cross-MCP availability note and the inline '(site: demo.royalplugins.com)' tag, which merely restate the site_id enum.

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 return contract and does it well: element_type, widget_type, depth, has_children, child_count, and raw settings, plus the not-found shape. Combined with the stated permission prerequisite, an agent has enough to call it correctly; only edge details like settings normalization or size limits are absent.

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 all three parameters are already documented in the schema, including element_id format and the site_id enum. The description only adds the permission linkage to post_id and the 'by its ID' scoping, which is marginal beyond structured fields — 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 ('Read the full settings object for a single Elementor element') and scopes it to one element identified by ID, covering all element kinds (widget, container, section, column). This is clearly separable from elementor_get_page_outline (whole tree) and elementor_get_kit_globals (global kit data).

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?

Explicitly sequences usage: 'Use after elementor_get_page_outline to inspect a specific element before proposing a modification.' That gives both the prerequisite and the intent. It does not name exclusions or competing siblings such as the emcp-tools-get-element-settings variant, so it falls short of a full when/when-not treatment.

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