list_clients

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

Annotations already declare readOnlyHint=true, so the safe-read profile is covered. The description adds that the response is paginated and names the pagination fields (page, last_page, total), which is useful return-shape context, but says nothing about default ordering, page size behavior, or what happens with the query filter.

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 with zero filler, and the purpose is front-loaded. The brevity is not wasteful in structure but crosses into under-specification, since almost nothing useful beyond the verb and a return-shape fragment is conveyed.

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?

This is a moderately complex tool: six parameters, a query-filter mini-language, an enum fieldset, and no output schema. Two terse sentences do not cover that surface, and there is no output schema to fall back on for return-value semantics, so an agent would need to read the schema closely to call it well.

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 a middling 67%, and the description adds essentially no parameter meaning beyond the schema — it only echoes pagination concepts already implied by the "page" parameter. The most complex parameter, the Fatture in Cloud query filter "q", is documented solely in the schema, and the description does not clarify it or the company_id default.

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?

The description gives a clear verb and resource ("Elenca cliente" = list clients), so the basic action is identifiable. However, it offers no differentiation from the many sibling tools that also deal with clients (get_client, client_statement, lookup), leaving the agent to infer scope from the name alone.

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?

There is no guidance on when to use this list tool versus get_client or client_statement, and no mention of supported filtering or sorting use cases. The only contextual hint is that results are paginated, which implies browsing rather than a single-record fetch.

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