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

Annotations already establish readOnly/idempotent/non-destructive, so the safety profile is covered; the description adds real context beyond that — the builder-data-vs-post-content distinction and the drill-down behavior of `element`. It does not mention pagination semantics or rate/size limits on the listing.

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?

Four sentences, front-loaded with the purpose then the prerequisite then the mechanism; each sentence carries information. Slightly dense packaging (the builder list and the drill-down detail compete for attention) but no 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?

An output schema exists and annotations cover the safety profile, so the description only needs the workflow context and the element-drill-down behavior — both are present. The remaining gap is that site_url and pagination expectations for a multi-site connector are unstated.

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%, and the description meaningfully explains only one of five parameters (`element`: pass an id from the list to get that element's full settings, including colours, typography, spacing). id, limit, offset and site_url are left to inference; limit/offset are conventional but site_url is not explained.

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?

Specific verb+resource ("Inspect how a WordPress page is actually built") with the concrete scope spelled out: Elementor, WPBakery, Gutenberg, classic, plus reading editable design fields. An agent can distinguish this from wordpress_get_post or wordpress_update_post without opening the schema.

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?

Explicit sequencing guidance — "Call this BEFORE editing a page" — and a concrete failure mode explaining why (on Elementor the visible design lives in builder data, so a plain content update changes nothing). It stops short of naming the sibling write tool (wordpress_edit_page_design) as the follow-up, so it's clear context rather than full when/when-not routing.

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