wp_elementor_add_repeater_item

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

With no annotations provided, the description carries the full disclosure burden. It conveys that the operation is additive ('append', 'add a...') rather than destructive to existing items, and it flags a real behavioral constraint: item fields must match the widget schema. It does not disclose return values, persistence or CSS-regeneration side effects, or behavior when element_id does not reference a repeater widget — gaps that matter for a mutation tool with zero annotation coverage.

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?

One front-loaded sentence states the action before concrete examples, followed by a short operational directive. There is no filler and both clauses earn their place, making the definition appropriately sized for its scope.

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 tool has a nested flexible object, no output schema, and no annotations, so completeness depends on the description plus the parameter schema. Together they provide the key operational steps (target page, element_id from wp_elementor_list_elements, schema-matching fields), but the return value and side effects of the mutation are left unstated. That is adequate for making the call but not fully complete.

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 the item parameter itself already carries rich per-widget field examples (image-carousel, jet-testimonials) plus page_id and element_id semantics. The description's 'provide item fields matching the widget schema' reinforces but does not extend the schema's guidance, so the baseline 3 applies.

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 opens with a specific verb+resource pair ('Append a new item to an Elementor repeater widget') and grounds it with concrete examples (carousel slide, testimonial, photo). The 'append' verb clearly differentiates it from wp_elementor_update_repeater_item and wp_elementor_remove_repeater_item, and from wp_elementor_insert_widget which adds whole widgets rather than items within them.

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 examples ('add a carousel slide, testimonial, photo') give an agent concrete context for when this tool applies, and the directive to 'provide item fields matching the widget schema' sets operational expectations for the call. It does not, however, name alternatives or state when not to use it (e.g., versus wp_elementor_update_repeater_item for modifying an existing slide), so it stops short of explicit routing.

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