duplicate_elementor_page

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

The description discloses key behavioral details: it creates a new draft page, copies specific fields (_elementor_data, etc.), and flushes CSS. This goes beyond the annotations (destructiveHint: false, idempotentHint: false) by explaining the side effects, though it could mention the need for permissions.

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 extremely concise with two sentences. Every word serves a purpose; no fluff. It is front-loaded with the main action and quickly lists the copied fields and side effect.

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 duplication tool with 4 parameters and an output schema, the description covers the main aspects: what is duplicated, the action taken, and the CSS flush. It lacks mention of prerequisites (e.g., Elementor must be active) or error states, but these are minor given the output schema exists.

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 low (25% for new_title). The description adds meaning by stating that new_title defaults to '<original> (Copy)' and that the page is created as a draft, partially compensating for missing schema descriptions. However, it does not explain site_id or source_page_id beyond 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 clearly states the tool's purpose: 'Duplicate an Elementor page within the same site.' It specifies the verb (duplicate), resource (Elementor page), and context (same site), distinguishing it from siblings like duplicate_widget or list_elementor_pages.

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. It does not mention any prerequisites, error cases, or scenarios where another tool might be more appropriate, such as when duplicating a page without Elementor data.

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