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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavior: a human-approval gate enforced through confirm, and a serialization constraint that only one restore may be in flight. It does not say what page state is overwritten or whether a pre-restore backup exists.

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?

Three short sentences, front-loaded with the action, then the confirmation precondition, then the concurrency constraint. Nothing is padded or restated.

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, non-idempotent mutation with no output schema and four required parameters, the definition covers the approval workflow and sequencing well. It remains incomplete on the post_id parameter and on the practical consequences of the restore (what is replaced, whether it can be undone), which matters for a destructive operation.

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 only 25% (site_id alone), so the description has to carry weight: it explains that rollback_id identifies the snapshot and that confirm must be true only after approval. post_id is left completely undefined in both schema and description, which is the main gap for a 4-parameter destructive tool.

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 states a specific verb and resource ('Restores a private Elementor rollback snapshot by rollback_id'), so an agent knows exactly what operation it performs. It does not, however, point at the sibling wp_elementor_list_rollbacks, which is where a rollback_id would come from, so it stops short of full sibling differentiation.

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 concrete when-to-use rules: obtain user approval before calling, pass confirm=true only after that approval, and restore only one rollback at a time while awaiting the result. It omits explicit alternatives (e.g., listing rollbacks first to obtain an id), so it is clear context rather than complete routing guidance.

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