list_f24

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

readOnlyHint=true already tells the agent this is a safe read, so the description's main contribution is disclosing the paginated return shape (page, last_page, total), which is genuinely useful given there is no output schema. It does not mention default page size, cost of large fieldset=detailed responses, or any rate limits.

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 and followed by the return shape; nothing is wasted. It is perhaps too terse for a six-parameter list tool, but there is no padding.

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 read-only list tool with no output schema, disclosing pagination fields is the right instinct, but with six parameters (filter syntax, sort, fieldset, company defaulting) the definition leaves the agent to rely entirely on the schema. It is minimally adequate rather than complete.

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 67% and the description adds no meaning beyond it — "page" appears only as part of the response shape, not as parameter guidance. The schema itself documents q, sort, fieldset and company_id, while page and per_page carry no descriptions in either place, so the description fails to fill that residual 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?

"Elenca modello F24" gives a specific verb (list) and resource (F24 forms), which is enough to separate it from get_f24/create_f24/update_f24 in the sibling set. It stops short of explicitly naming those siblings or stating the scope of what is listed, so it is clear but not fully differentiated.

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 when-to-use guidance at all: nothing says to use this instead of get_f24 for a single record, or when filtering via q is preferable to listing everything. The agent must infer the list-vs-get distinction purely from the verb in the name.

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