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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds 'returns all' and optional filtering, but the read-only sentence is largely redundant with annotations and no pagination or result-size behavior is disclosed.

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 is front-loaded and the description is short, but the final sentence about Royally marking it read-only is redundant with annotations and does not earn its place. The core content is efficient, but not waste-free.

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?

For a simple read-only list tool with fully described parameters and rich annotations, the description covers what is returned and how filters work. However, with no output schema, it should do more to clarify return shape, pagination, or limits, especially since it claims to return 'all' matching content.

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 the schema itself fully documents all three parameters. The description mentions post_type and status filtering, but does not add meaning beyond the schema and does not mention site_id.

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 description states a specific verb and resource: returning WordPress pages and posts built with Elementor. It is clear enough to distinguish from generic page/post tools, though the name says 'list-pages' while the description includes posts, creating slight ambiguity against the sibling list-posts tool.

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?

It implies the tool is for listing Elementor-built content and notes optional post_type/status filters, but it does not explicitly say when to use this instead of list-posts, get-page, or get-post. Usage is inferable but not guided.

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