wp_elementor_list_repeater_items

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

No annotations are provided, so the description carries the full behavioral burden. The verb 'List' and the phrase 'all items' imply a non-mutating read operation with no filtering, which is useful. However, it does not disclose what the returned items look like, whether item IDs are included for use with update/remove repeater tools, or how invalid element IDs are handled.

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 focused sentence that leads with the core action, then adds concrete examples and supported ID contexts. Every part earns its place; there is no filler or redundant elaboration.

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 two-parameter read-only list tool with fully described schema properties, the description is nearly complete. It names the exact resource, gives real-world widget examples, and states valid ID sources. The main gap is the absence of an output schema or any statement about the return structure, but this is minor given the low complexity of the operation.

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%, and both page_id and element_id already have clear descriptions. The tool description adds no new parameter-level meaning beyond what the schema provides; it mostly restates that page IDs and template IDs are supported, which is already present in the schema.

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 names a specific verb and resource: 'List all items in an Elementor repeater widget.' It additionally gives concrete widget examples (carousel slides, testimonials, photo roller images) and clarifies that both page IDs and Theme Builder template IDs are supported, which clearly distinguishes it from sibling tools like wp_elementor_list_elements.

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 clearly establishes the intended use case: retrieving all items inside a repeater widget, and it explicitly states valid input ID types (page IDs and Theme Builder template IDs). It does not explicitly compare against alternatives or state exclusions, but the resource scope is specific enough that an agent can infer when this tool is appropriate.

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