list_payment_accounts

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description contributes the response envelope (page, last_page, total), which is genuinely useful since no output schema exists, but it says nothing about result volume, default page size, ordering, or the fact that the q parameter accepts a Fatture in Cloud filter expression — behavior an agent would need to know to call it well.

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 resource definition and followed by the response shape; nothing is padded or repeated. The second sentence is slightly ambiguous because page/last_page/total could be read as input parameters rather than response fields.

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 six optional parameters, no output schema and a non-trivial Fatture in Cloud filter syntax, a definition that only spells out the pagination envelope is adequate but thin. It covers the return shape (helpful given no output schema) yet leaves the agent without guidance on filter syntax, fieldset tradeoffs, or company_id fallback behavior beyond what the schema states.

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 67%, so the schema already documents q, sort, fieldset and company_id with their own descriptions. The description adds only the pagination vocabulary (page, last_page, total), and those are response concepts rather than explanations of the per_page/sort/q semantics. It therefore lands at the baseline rather than compensating for the undocumented page/per_page bounds.

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 uses a specific verb ("Elenca") plus a concrete resource ("conto di saldo") and disambiguates the concept by naming the concrete forms: banca, cassa, carta. It also states the business role (accounts on which receipts and payments are registered). It does not explicitly contrast itself with the nearby list_payment_methods sibling, so the boundary between 'account' and 'method' is left for the agent to infer.

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?

Usage is only implied: the agent can infer it should call this to discover accounts before registering incassi/pagamenti. There is no explicit when-to-use, when-not-to-use, no mention of prerequisites (e.g. company scoping), and no routing to alternatives such as list_payment_methods or get_payment_account.

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