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

Goes well beyond the annotations: the URL is anonymous (no WP login), time-limited, frozen to a snapshot, and expires; edit_url persists across sessions and requires edit-capable login. That is exactly the context annotations (readOnlyHint=false, openWorldHint=true) cannot convey. The trailing 'Through Royally: waits for a person to approve it... no undo' sentences describe a mutation-approval flow that doesn't obviously apply to a preview-link creation, muddying an otherwise strong disclosure.

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 PURPOSE and WHEN TO USE sections are tight, front-loaded and skimmable. However, the final Royally paragraph about human approval and 'this connection has no undo' is boilerplate unrelated to generating a preview link and consumes attention without earning it.

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 names the returned fields (`url` and `edit_url`) and their differing lifetimes, which is the information an agent most needs. The only gap is the ambiguous Royally/undo passage, which leaves unclear whether this call has side effects requiring approval.

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 and site_id are already documented, and the enum on site_id is in the schema. The description only implies the target via 'current Elementor content of a post' — baseline 3 applies when the schema does the heavy lifting.

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?

The first line states a specific verb and resource ('Creates a signed, time-limited URL that renders a snapshot of the current Elementor content of a post') with the crucial qualifier 'without publishing it'. It also distinguishes the two return values (url vs edit_url) so an agent knows this is not the same thing as a public share link.

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 scopes use to 'Agent self-validation only', names the exact trigger (right after `elementor/build-composition`, `elementor/manage-elements`, `elementor/update-page-settings`), and states the follow-up action (fetch url with browser/screenshot tool). It also gives a clear when-not: do not hand `url` to the user, use `edit_url` instead.

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