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 adds real context beyond that: it flags the data as sensitive payroll information and documents the paging contract ('pass next_page as page') plus the underlying endpoint. It stops short of describing what a payslip record contains or any auth/rate-limit constraints.

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 purpose, then sensitivity, then paging. Efficient overall, with only mild redundancy in the pagination sentence that echoes the schema's own page description.

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 filtered list with four fully documented optional parameters and no output schema, the description covers purpose, filters, sensitivity and paging adequately. The remaining gap is that it says nothing about what a payslip record contains or the shape of the paged response, which an agent may want before calling.

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 four parameters (page, year, employee, monthly_pay) are already documented in the schema. The description's pagination note is essentially a restatement of the page parameter's own description ('Use next_page from the previous reply'), adding no syntax or format detail the schema lacks. Baseline 3.

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 employee payslips') plus the optional filter dimensions (employee, year, month). It is clear what the tool returns, though it never distinguishes itself from the close sibling jethr_list_payrolls, so an agent must infer the boundary.

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?

The 'optionally for one employee, year or month' phrasing implies when the filters apply, and 'Sensitive payroll data' hints at a caution posture. But there is no explicit guidance on when to use this versus jethr_list_payrolls or the payslip deduction tools, and no stated prerequisites (e.g., needing an employee uuid from jethr_list_employees, which is only mentioned in the schema).

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