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

Annotations already declare destructiveHint=true/readOnlyHint=false, and the description goes well beyond them: it documents the dry-run → confirm_id write flow, two distinct failure outcomes (not_supported, title_over_limit), and the tool's auto-resolution of which attribute the product type exposes. This is exactly the behavioral context a mutation tool needs.

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?

Every clause is load-bearing (attribute naming, fallback, constraint, dry-run flow), and the primary action is front-loaded. It is dense and code-switches between Italian and English, which slightly hurts scannability, but nothing is filler.

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, no-output-schema mutation tool, the description covers failure modes, the dry-run protocol, the title-length precondition, and the fallback path, leaving nothing an agent must infer before calling 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?

Schema coverage is 83%, so the schema carries most parameter docs; the description adds the workflow meaning that ties confirm/confirm_id together (dry-run vs real write) and reiterates the ≤125-char highlight constraint. It adds marginal value beyond the schema but does not fully compensate for the title-length dependency, which it describes only in prose.

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?

It states a specific verb+resource (update the Item Highlights / title_differentiation attribute on a listing) and clarifies the official-vs-legacy attribute naming, which no sibling tool does. An agent can distinguish it from update_listing, bulk_update_listings, or create_listing immediately.

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 explicit when-to-use (call without confirm for dry-run, confirm=true to write), an explicit fallback (not_supported → use bullet_point via update_listing), and a prerequisite (title must be ≤ 75 chars or title_over_limit stops the call). Alternatives and exclusions are both named.

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