list_products

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

The readOnlyHint annotation already establishes this is a safe read, but the description adds genuinely new context by disclosing the paginated response shape (page, last_page, total). It still says nothing about default page size, maximum per_page, or how company_id fallback resolution behaves, which matters for a list call.

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 short sentences, front-loaded with the operation and followed by the response contract, with no filler. The telegraphic style leaves it terse but nothing 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?

For a six-parameter list tool with no output schema, the description covers the operation and the pagination envelope but omits filtering semantics, default behavior, and result ordering. Adequate to call correctly with the schema in hand, but not self-sufficient.

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?

At 67% schema coverage the schema already documents q, sort, fieldset and company_id, so the baseline is 3. The description only reinforces the page parameter through the response-shape sentence and adds no meaning to per_page, sort syntax, or the default fieldset behavior.

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 ('Elenca prodotto o servizio a listino') and clearly distinguishes itself from the sibling CRUD operations get_product/create_product/update_product/delete_product. However the phrase 'a listino' is slightly ambiguous about whether this lists products generally or only catalogued items.

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?

No guidance on when to use this versus the near-identical sibling list_price_lists or get_product for a single item. There are no stated prerequisites, no exclusions, and no mention of how filtering or pagination should drive the choice.

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