wordpress_clone_page

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

No annotations are provided, so the description must carry the full burden. It reveals the result is a draft page but omits critical details: whether the clone is deep (copies all content/metadata), any limitations (e.g., doesn't copy revisions), or side effects. The description is insufficient for a mutation operation.

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 concise sentence, but it could be improved by front-loading the action and result for faster scanning. No unnecessary words, but structure is minimal.

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?

Given the complexity of cloning and the presence of many sibling tools, the description is too sparse. It lacks details about return values (no output schema), edge cases (e.g., cloning with same title or slug), and whether the cloned page inherits all attributes. More context is required for an AI agent to use it correctly.

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?

With 0% schema description coverage, the description compensates partially by implying sourceId is the existing page and title is the new title. However, the optional 'slug' parameter is not explained, and there is no explicit mapping of parameters to their roles. The description adds value but not enough to fully clarify all parameters.

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 action ('clone'), the resource ('existing WordPress page'), and the result ('new draft page'). It effectively distinguishes from sibling tools like wordpress_create_page (create from scratch) and wordpress_update_page (modify existing).

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 usage for duplicating an existing page, but lacks explicit guidance on when to use this tool versus alternatives like wordpress_create_page or when not to use it (e.g., if source page does not exist, insufficient permissions). No prerequisites or exclusions are mentioned.

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