leggi_seo_prodotti_selezionati

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

No annotations are provided, so the description carries the full burden. It discloses that it is a read (same content as leggi_seo_prodotto) and that it works on legacy products, but not how it behaves with invalid or missing ids, partial failures, or empty input. Adding the legacy-product nuance is real value, but key mutation/error semantics remain undisclosed.

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, front-loaded with the core behavior, followed by useful context. The parenthetical is efficient; the 'ottimizza SEO' button reference is slightly implementation-flavored but earns its place as usage guidance.

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 an output schema present, the description need not explain return values, and for a single-parameter batch reader it covers purpose, batch semantics and usage context. The main residual gap is error/behavior disclosure given the absence of annotations.

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 0%, but the sole parameter 'prodotto_ids' is self-describing and the description clarifies batch semantics ('per ciascun id'), telling the agent results are produced per id. This adds meaning the bare schema does not, though it could say what happens for absent ids.

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 ('SEO status of a selection of products in a single call') and explicitly contrasts with the sibling leggi_seo_prodotto by saying it returns the same content per each id. An agent can tell this is the batch variant of a single-product reader without opening any schema.

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 concrete usage context: it is meant for the plugin's 'ottimizza SEO' button and works on products loaded before the plugin, not just those just created with scansiona_cartella_prodotti. It stops short of an explicit when-not or naming the single-product alternative as the choice for one id, so it is clear context without explicit exclusions.

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