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

Annotations already declare readOnlyHint=false, destructiveHint=true, openWorldHint=false, so the safety profile is conveyed structurally. The description adds that restoration draws from a registry and enumerates which fields get overwritten, but it does not say what happens when no prior record exists or whether the rollback is all-or-nothing.

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?

A single sentence with the action and the affected fields front-loaded, and no filler. The '(SCRITTURA)' tag is compact and useful for signalling a write operation, though the parenthetical style is slightly terse.

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?

No output schema exists, but the description names all fields restored and the source of the prior state; annotations carry destructiveness and the schema carries the confirm_id protocol. Only edge-case behavior (missing registry entry, partial rollback) is left unstated.

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 100%, so batch_id, account_id and confirm_id are fully documented in the schema, including the two-step confirm flow. The description only echoes 'un lotto' and adds no format or constraint detail beyond that, so the baseline 3 applies.

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?

States a specific verb and resource: it restores (rimette) title, generic_keyword, bullets and description to their state before a batch, sourced from the registry. That is clearly distinct from apply_title_seo_batch or plan_title_seo_fix, though no sibling is named explicitly.

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?

Usage is only implied by 'prima di un lotto' — an agent can infer this is an undo for a previously applied batch. There is no explicit when-to-use / when-not-to-use statement and no mention of the preview-plus-confirm prerequisite (that lives only in the schema's confirm_id field).

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