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

Annotations already declare read-only, idempotent, non-destructive, so the safety profile is covered; the description adds non-obvious value with a response-size budget (~2KB typical) and the cost of include_styles (~2-4x). It also confirms read-only execution ("runs straight away"). It does not cover failure modes (invalid post_id, non-Elementor pages), which keeps it at 4.

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-loads the core purpose and return shape in the first sentence, with the usage hint and the include_styles tradeoff following in a logical order. Slightly dense with parentheticals (including the leading "Also available" bracket and the trailing site/read-only note), but no sentence is 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 carries the burden of describing returns, and it does so concretely (hierarchy, widget types, text snippets, optional styles object, approximate size). Combined with annotations covering side effects, an agent has enough to call it correctly; only the post_id semantics and error behavior are unaddressed.

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 coverage is 67%; the schema documents include_styles and site_id, but the description adds real meaning by quantifying the tradeoff ("adds ~2-4x to response size") for include_styles. post_id carries no description in schema or description text, leaving ambiguity about whether it accepts pages, posts, or templates.

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 (extract a simplified outline of an Elementor page) and enumerates exactly what the outline contains: section/container hierarchy, widget types per slot, and short text snippets. This differentiates it from raw-structure siblings like get_page_structure, which returns the full _elementor_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 gives a use case ("useful before calling clone or replace_text to understand the structure first") and notes include_styles as the switch for design-oriented reasoning. The "Also available: elementor/build-composition, elementor/get-page-structure" line names alternatives but doesn't state the condition that would select them instead, so routing is implied rather than explicit.

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