Read an Elementor page

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds useful context on what summary vs raw produce, but says nothing about tree size, depth limits, pagination, or what happens for pages with no Elementor data.

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 tight sentences with the core purpose front-loaded before the format behavior. No filler, though the second clause is somewhat compressed and omits the 'both' case.

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 and no parameter descriptions, the description needs to carry more weight; it covers the two primary formats but leaves 'both' undefined and gives no sense of return shape or size. Adequate but with clear gaps for an agent choosing a format.

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%, so the description carries the burden, and it explains the summary and raw format values usefully. However, the enum's third value 'both' is never explained, and post_id semantics (post ID of the target page) are left entirely to the schema.

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 ('Read the Elementor tree for a page'), which is clear and distinct from write-oriented siblings like wp_el_set or wp_el_patch. It does not, however, distinguish itself from wp_el_snapshots, which an agent might reasonably confuse with reading page structure.

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 gives a genuine selection rule between two of the three formats (summary vs raw), noting raw is for 'precise edits'. It offers no guidance on when to prefer this tool over siblings such as wp_el_snapshots or wp_content_get, so usage is implied rather than fully framed.

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