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 fully covered externally. The description adds genuine value by describing the returned node shape, but its "its server marks it read-only, so it runs straight away" sentence merely restates the annotation rather than adding new context (no mention of failure modes for non-Elementor posts).

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?

Front-loaded: the verb and resource lead, return shape follows, and the sentences are short. The final clause about the server marking it read-only is largely redundant with annotations and is the one piece of filler.

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 spells out the returned tree structure, which is the key unknown for this tool. It omits edge cases (non-Elementor post, empty page, behavior when post_id is invalid), but for a read-only, fully documented 4-param tool it is close to sufficient.

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 post_id, site_id, summary and max_depth are already well documented with enums and defaults. The description says nothing about any parameter, not even the existence of a lighter summary mode or depth limiting, so it adds no meaning beyond the schema. 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?

A specific verb+resource ("Returns the element tree for an Elementor page") plus a concrete inventory of what the tree contains (containers, widgets, nesting, per-element ID/type/widget type). An agent immediately knows what it gets. It never names a sibling such as get-page-html or find-element, so the boundary with those tools must be inferred.

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?

No explicit when-to-use, when-not-to-use, or alternative is given despite close siblings (get-page-html, get-element-settings, find-element, elementor-get-page-structure). The use case is only implied by the stated purpose; nothing routes an agent between the competing structure-inspection tools.

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