wp_elementor_duplicate_page

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

Discloses remapped element IDs and the confirm requirement in safe mode, but with no annotations, it does not fully address aspects like fail behavior when source is not Elementor or default status.

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?

Two sentences, no redundancy, front-loaded with core purpose. Concisely states the essential information.

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?

Lacks explanation of safe mode, default behavior for under-specified parameters, and return value. Given the tool's complexity (5 params, safety feature), the description is minimal.

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?

Only explains the confirm parameter conditionally; title, slug, and status lack descriptions both in schema and description. With low schema coverage (20%), the description should compensate but does not.

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's action (duplicate), the resource (Elementor page), and the outcome (new draft with remapped element IDs). This distinguishes it from siblings like create or clone element 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?

Only mentions the need for confirm:true when safe mode is on, but does not provide guidance on when to use this tool versus alternatives, or prerequisites like checking safe mode status.

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