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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely useful behavior beyond that: it returns content with MIME type, text resources come back as strings, JSON resources are serialized to JSON strings. The closing "runs straight away" line only restates the read-only annotation, adding no new information, which keeps it out of 5 territory.

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 lead sentence and return-value explanation are front-loaded and earn their place, but the 'Input:' block duplicates the schema verbatim and the final 'Through Royally: its server marks it read-only' clause is a redundant vendor-stitched sentence that restates the annotation.

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?

There is no output schema, so the description rightly explains the return shape (content + MIME type, JSON serialization). For a single-required-parameter read tool with strong annotations that is nearly sufficient; only error/permission behavior for an invalid URI is 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 100%, and the schema's own uri description already says to use list-resources for discovery, so the description is largely restating it. The site_id parameter is never mentioned in the description at all. Baseline 3 is appropriate when the schema carries the semantics.

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 ("Fetches the content of an Elementor MCP resource by URI") and implicitly contrasts with the discovery sibling by directing the agent to list-resources first. An agent can distinguish this read-a-resource tool from list-resources and from page/widget getters without opening a 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?

Explicitly states the prerequisite flow: "Use list-resources first to discover available URIs," naming the sibling and the condition that selects it. It doesn't state when to prefer this over higher-level readers like elementor-get-page-structure, but for a generic resource reader the guidance is clear.

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