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

Annotations already declare destructiveHint=true, openWorldHint=true and idempotentHint=false, so the description only needs to add texture — and it does: pages are created OR reused, assignments are overwritten, and matching trashed pages may be restored and published, which is the non-obvious side effect an agent needs warned about. It does not say what is reported back (which pages were created vs. reused vs. skipped), which is the remaining gap.

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, both earning their place: the first front-loads the full scope of side effects, the second carries the safety gate. No filler or restatement of the title.

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 destructive, open-world maintenance operation with no output schema, the description covers scope, side effects, and the confirmation gate adequately. What is missing is any hint of the result shape (created/reused/restored counts) or failure behavior, which leaves the agent guessing about what to report after the call.

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 coverage is 100% and both parameters are documented in-schema, including that site_id must come from list_sites. The description only reinforces the confirm=true semantics that the schema already states, adding no new parameter meaning beyond baseline.

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 uses specific verbs against a specific resource set: create or reuse missing WooCommerce pages, update page assignments, restore and publish matching trashed pages. Nothing in the sibling list does page provisioning, so the operation is distinguishable, though it never names an alternative or states the boundary with generic page tools like wp_elementor_list_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?

It gives a concrete precondition for invoking: ask the user for confirmation before calling with confirm=true. That tells the agent how to sequence the call safely. It stops short of describing when the tool is unnecessary (e.g., when pages already exist and are assigned), so it is clear context without exclusions.

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