wp_elementor_remove_repeater_item

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does disclose the confirmation requirement when safe mode is on, which is useful, but it does not state whether the removal is permanent or how remaining item indices are affected.

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 two tight sentences with no filler. The core action and target come first, and the safe-mode requirement is stated succinctly without restating schema fields.

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?

The description is adequate for basic invocation, covering the operation, the indexing semantics, and the confirmation condition. However, it does not mention return values, irreversibility, or reindexing behavior, and no annotations compensate for these omissions.

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 baseline is 3. The description adds value by clarifying that the index is zero-based and explaining the confirm parameter's role in safe mode, going beyond the schema's basic field descriptions.

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 the exact action (remove), the resource (Elementor repeater widget), and the indexing scheme (zero-based index). This clearly communicates the tool's function and distinguishes it from the sibling add/update repeater tools.

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 implies this tool should be used when removing an item from a repeater, and the schema's index parameter references wp_elementor_list_repeater_items. However, there is no explicit when-to-use or when-not-to-use guidance, nor any direct comparison with the add/update repeater sibling tools.

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