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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered by structured data. The description adds one genuinely useful behavioral detail: each material echoes the requested id in 'inputs' so the caller can map outputs back to inputs (relevant for a batch lookup). It still says nothing about error behavior when an id is not found or partial-result semantics.

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 tight sentences with no filler; the retrieval action and the 20-item cap are front-loaded, and the input-id provenance follows. Slightly compressed phrasing but nothing 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?

For a nested-object tool with 0% schema description coverage and no output schema, the description covers the core lookup and the id-echo behavior but omits the nested catalog/meta structure and any not-found handling. It is adequate but leaves real gaps an agent would have to guess at.

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 0%, so the description must carry the param burden, and it partially does: it clarifies that the 'ids' strings may be either product ids or material ids and that the batch caps at 20. It says nothing at all about the nested 'catalog' wrapper or the 'meta.ucp-agent.profile' URI parameter, leaving a sizable gap.

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 ('Recupera ... prodotti per id di prodotto o di materiale') and scopes the operation to at most 20 items. It distinguishes itself from search_catalog by naming it as the source of the ids, but gives no hint of how it differs from the sibling get_product, which also retrieves products by id.

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 implies usage by noting the ids come from search_catalog ('quelli restituiti da search_catalog'), which gives a caller a starting context. However, it never states when to prefer this over get_product or search_catalog, and there are no exclusions or prerequisites.

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