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

readOnlyHint=true already declares this is a safe read. The description adds genuinely useful context: it handles sensitive financial data and is paged, with a mechanical note on passing next_page as page. It does not describe what a page contains (page size, total counts, ordering), so it adds moderate value beyond annotations.

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, zero filler, with the core purpose front-loaded ahead of the sensitivity and pagination notes. Slightly telegraphic ('Paged: pass next_page as page') but every clause carries information.

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 three-param read-only list tool with full schema coverage and no output schema, the definition is adequate but omits two things an agent would want: the distinction from jethr_list_payslips and any indication of the response shape or page size. Complete enough to call, not complete enough to choose confidently.

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%, so all three parameters are already documented, including the 1-12/13-14 month semantics. The description adds only the pagination restatement ('pass next_page as page'), which duplicates the schema's page description. Baseline 3 applies.

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 and resource ('List the company's monthly payrolls') and names the fields returned (year, month, status, totals). However, it never distinguishes itself from the sibling jethr_list_payslips, which is a real ambiguity for an agent choosing between 'payrolls' and 'payslips'.

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 jethr_list_payslips or the other list siblings, no prerequisites, no exclusions. The only usage hint is pagination mechanics, which is not a selection criterion.

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