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

Annotations only say destructive=true/readOnly=false; the description adds far more: the dry-run VALIDATION_PREVIEW outcome, the not_supported refusal, the VINCOLO Amazon title-length precondition (title_over_limit stops the write), and the attribute-resolution behavior. This is rich context an agent cannot get from the annotations.

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?

Dense but front-loaded, and each clause (naming, support, title constraint, dry-run) earns its place. The mixed Italian/English phrasing and long parentheticals slightly hurt scannability, but no sentence is wasted.

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?

With no output schema, the description compensates by naming the key outcome codes (VALIDATION_PREVIEW, not_supported, title_over_limit) and the confirm flow. A mutation tool with real constraints is well covered, though the exact success return shape is not described.

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 already 83%, but the description adds meaning beyond it: highlights total ≤125 char tied to title_differentiation, confirm triggering the real write, and the ordering constraint that item_name must be ≤75 char first. The confirm_id/confirm relationship is implied but not spelled out further.

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+resource ('Update Item Highlights on a listing') and immediately clarifies the ambiguous naming: the official attribute is title_differentiation, item_highlights is the legacy name, and the tool self-resolves which the schema exposes. It is clearly distinguishable from the bullet_point family it routes to.

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?

Gives explicit when-not conditions (not all marketplaces/product types expose it; the tool refuses with not_supported) and names the alternative path (bullet_point via update_listing). It also prescribes the required workflow: call without confirm for dry-run, then confirm=true to write.

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