wp_elementor_list_elements

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

No annotations exist, so the description must bear the full burden. It discloses the return format as a flat index with specific fields, implying a read-only operation. However, it omits details like error handling (e.g., missing page), performance characteristics, or whether the list is exhaustive.

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 description is a single, concise sentence that immediately states the action (list), scope (all Elementor elements on a page), and key output fields. No unnecessary words—perfectly front-loaded.

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?

Given the simple parameter set and lack of output schema, the description covers the core functionality. However, it misses context about empty results, invalid page_id, or data format (e.g., id type). Slightly more completeness would help, but it's adequate for a straightforward tool.

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% for the single parameter page_id, described as 'WordPress page ID'. The tool description adds 'on a page' but does not enhance the schema's meaning. Baseline of 3 is appropriate as no extra clarification is needed.

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 clearly states the tool lists all Elementor elements on a page as a flat index, specifying the output fields (id, widgetType, text preview, is_editable flag). This distinguishes it from related siblings like wp_elementor_get_structure or wp_elementor_find_widgets, which serve different purposes.

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?

The description provides no guidance on when to use this tool versus alternatives. For instance, it does not compare with wp_elementor_get_structure or mention prerequisites like page_id validity. A user would benefit from explicit context.

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