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

readOnlyHint=true already declares the safety profile, so the bar is lower. The description adds genuinely useful behavior — the result is paged and the reply carries a next_page — but says nothing about page size, total counts, empty-result behavior, or what identifying fields each CCNL record contains.

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?

Three short sentences, front-loaded with what is listed, then the pagination mechanics. Zero filler. The raw endpoint path is arguably redundant metadata but it is cheap and front-adjacent to the paging note.

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 one-parameter, read-only list tool with a fully described schema, the description covers purpose and paging adequately, and the next_page mention implicitly signals a paged response envelope despite no output schema. Only the shape of an individual CCNL record is left unexplained.

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 100% and the schema's own text already states '1-based (default 1). Use next_page from the previous reply.', which the description largely repeats. With a single fully documented parameter, the baseline 3 applies; no additional semantics are contributed.

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?

Specific verb (List) plus a precisely named resource (national collective labour agreements / CCNL applied by the company), with the acronym expanded so an agent unfamiliar with Italian payroll terminology understands it. It does not explicitly contrast with the many sibling list_* tools, but the resource is unambiguous enough that confusion is unlikely.

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 implied by the name and by 'the company applies' — read the CCNL catalogue for the current company. There is no statement of when to prefer this over a sibling like jethr_get_contractor or jethr_list_payrolls, and no prerequisites or exclusions noted. The pagination instruction is invocation guidance rather than selection guidance.

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